Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 71 replies
  • Subscribers 6 subscribers
  • Views 265556 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

SophosScanD process consuming up to 95% CPU

Pelagus

Dear,

After downgrading my MacBook Pro from Mavericks back to Snow Leopard, I re-installed Sophos Free AV. It seems to work well, except that a SophosScanD process is almost constantly - with short intermittents - using up to 95% (on average, sometimes even more than that) CPU and heating up my machine. I have completely uninstalled and then re-installed the product, from your website, but it keeps happening.

Any ideas? Please let me know if you need more information.

Regards, Hans

:1018785


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

    Dear Bob,

    I downloaded and installed the free home-edition for Mac, again from scratch. Note that download from your website still provides the older version which contains the problem. I manually updated from the shield menu which led to another over-100MB download. It might be better to offer the most current -fixed- version right away as the inital download from the website.

    Anyway, as I initially had to re-install the buggy version it was clear that the problem was reproduced, SophosScanD started consuming over 95% again of CPU and my machine started heating up almost immediately. This ended abruptly after the update completed. Temperatures and CPU consumption are now back to normal. SophosScanD is no longer the most prominent process in the Activity Monitor although it is still present (apparently permanent) and appears to be using a lot of memory (93.3MB). It might still be helpful to understand what it IS and DOES exactly and why it would need so much of my machine's resources.

    While the CPU and heat problems appear solved for now, I am still not convinced that SophosScanD is behaving the way it should and I am eager to find out what will happen once the "virus detection data package" encounters another end of life warning.

    So far, so good.

    :1019157
Reply
  • 0

    Dear Bob,

    I downloaded and installed the free home-edition for Mac, again from scratch. Note that download from your website still provides the older version which contains the problem. I manually updated from the shield menu which led to another over-100MB download. It might be better to offer the most current -fixed- version right away as the inital download from the website.

    Anyway, as I initially had to re-install the buggy version it was clear that the problem was reproduced, SophosScanD started consuming over 95% again of CPU and my machine started heating up almost immediately. This ended abruptly after the update completed. Temperatures and CPU consumption are now back to normal. SophosScanD is no longer the most prominent process in the Activity Monitor although it is still present (apparently permanent) and appears to be using a lot of memory (93.3MB). It might still be helpful to understand what it IS and DOES exactly and why it would need so much of my machine's resources.

    While the CPU and heat problems appear solved for now, I am still not convinced that SophosScanD is behaving the way it should and I am eager to find out what will happen once the "virus detection data package" encounters another end of life warning.

    So far, so good.

    :1019157
Children
No Data
Unfiltered HTML