Guest User!

You are not Sophos Staff.

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

Why does it stop scanning for extended periods?

I started SAV on "Scan Local Drives" this morning (it's late afternoon now) and so far it's scanned less than 8% of my 5 million files. Oddly, it seems to just stop scanning for extended periods: the "Items Remaining" counter stops decrementing and nothing happens for several minutes. Then it starts up again. 

At this rate, it's going to take days to complete a scan, and meanwhile my system is rather sluggish. I don't even know if it's worth waiting for it to finish. 

Anyone else seen this? 

:1001651


This thread was automatically locked due to age.
Parents

  • RobLewis wrote:

    The funny thing is, it's running 2 AVAgent processes, but combined I'm seeing only about 40% peak CPU (and usually no more than 20%), 

    Maybe the long delays are when it's scanning a disk image file; I have a few of those. Can it see the individual files in disk images? 


    The UI increments when each file has completed scanning.  Disk images, zip files, Java jar files, and other archives (such as sparsimage bundles used by Time Machine) are each considered a "file" and so the progress bar doesn't... progress when that "file" is being unpacked and the contents scanned.  I've already made a note to the UI team that there should be a change made to indicate archive contents are indeed still being scanned in these cases.  Right now the indication to watch for is whether the progress bar is still pulsing.  If this stops (no motion in the bar at all, not just a stall in forward motion), then scanning progress has also stopped.  Otherwise, it's just a really large file that requires a lot of unpacking and further attention.

    :1001661
Reply

  • RobLewis wrote:

    The funny thing is, it's running 2 AVAgent processes, but combined I'm seeing only about 40% peak CPU (and usually no more than 20%), 

    Maybe the long delays are when it's scanning a disk image file; I have a few of those. Can it see the individual files in disk images? 


    The UI increments when each file has completed scanning.  Disk images, zip files, Java jar files, and other archives (such as sparsimage bundles used by Time Machine) are each considered a "file" and so the progress bar doesn't... progress when that "file" is being unpacked and the contents scanned.  I've already made a note to the UI team that there should be a change made to indicate archive contents are indeed still being scanned in these cases.  Right now the indication to watch for is whether the progress bar is still pulsing.  If this stops (no motion in the bar at all, not just a stall in forward motion), then scanning progress has also stopped.  Otherwise, it's just a really large file that requires a lot of unpacking and further attention.

    :1001661
Children
No Data