06-28-2011 01:06 PM
Intercheck is using 98% of my %CPU for long periods of time. If I kill it, it comes back and climbs to 90%. Is there a way to fix this?
Threat detection engine: 3.20.2
Threat data: 4.66
Release date: June 6, 2011
Protects against 2623390 threats
Solved! Go to Solution.
06-28-2011 01:17 PM
06-29-2011 07:56 PM
No. I only use Safari. I generally have Safari, Eudora, Photoshop CS5.5, Dreamweaver and GraphicConverter open when I notice this. I also use several application enhancers.
06-30-2011 03:02 PM
You can try running SDU mentioned here:
Then I can send you a location to email it to. I'm not sure it'll capture all the information needed, but it will likely capture enough to at least point out what interaction is causing the issue.
07-25-2011 09:52 AM
I'm on a MBP 5,3 Mac OS X 10.6.8 and I use Chrome as my primary browser. Is there a fundamental incompatibility between Sophos and Chrome?
There's no fundamental incompatibility, but Chrome's built-in PDF viewer does some non-standard things when downloading a PDF -- it chunks it into viewable cache files so you can start viewing the PDF when the first page is downloaded. As a result, downloading a PDF can result in more than 150 cache files showing up and being quickly rewritten on the computer -- and on-access scanning attempts to scan each one of these as it is created/modified. This usually works well, unless that cache file happens to have compressed PDF segments in it that include the header but not all the data... at this point, on-access attempts to decompress the segment until it is sure it can't do anything with the available data, and then rushes on to the next segment.
As a result, previewing a PDF in Chrome can sometimes result in on-access scanning having more than 500 individual scans to run on the single PDF. It gets the job done eventually, but as you've noticed, things slow down for a while while the engine attempts to control the filestorm.
However, this was pre-7.3; I think that the dev team has made some improvements on our side to mitigate the effects of Chrome's behaviour, so this might not be an issue anymore. Is anyone able to peg their CPU using the Chrome PDF viewer using 7.3.1?
07-25-2011 12:41 PM
This problem has nothing to do with chrome even without chrome and on 7.3.1 the problem is there. And it maxes out your CPU so much and so prolonged that you have to fear for the health of your computer. Intercheck has no problem to use more than 100 percent (how can that be?) of your macbook. As it does with me under 10.7.
It makes Sophos behave like a virus that is spread to destruct your computer! And this is a very BAD behaviousr for a virus-fighter!
I believe Sophos should WARN users for this kind of destructive behaviour of it's application.
07-25-2011 01:48 PM
Lemon, the issue you are describing with backups on Lion is not the same issue I am responding to in this thread, even if both result in one of the CPU cores reaching 100%. The reason you can see more than 100% CPU usage is that the system has more than one CPU core; for a dual-core system, your max usage is 200% (100% on each core). For a quad-core system, the max usage is 400%.
This is definitely something you don't want to see happening on a laptop running on battery power (for obvious reasons), but Apple computers should be designed to easily handle CPUs running at 100% (or even 200%). There should be no reason to fear for the health of your computer, although it will warm up and pump out more exhaust heat. For the issue described in this thread, one of the cores will hit 100% for a few minutes before going back to normal levels.
This is not destructive, although it will draw significantly more power while the CPU core is running at full capacity.