Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 27 replies
  • Subscribers 6 subscribers
  • Views 27196 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Intercheck maxes out my CPUs

Kernos

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?

TIA, 

Bill

Sophos Anti-Virus

7.3.0.C

Threat detection engine: 3.20.2

Threat data: 4.66

Release date: June 6, 2011

Protects against 2623390 threats

OS 10.6.8

:1003241


This thread was automatically locked due to age.
Parents
  • 0
    RationalAdult wrote:

    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?

    Thanks


    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?

    :1003545
Reply
  • 0
    RationalAdult wrote:

    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?

    Thanks


    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?

    :1003545
Children
No Data