Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 6 subscribers
  • Views 3741 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

memory hog

euripides

I've installed and run the Sophos free a.v. for the Mac for several weeks, and the machine has become increasingly sluggish. I finally checked memory use and the a.v. program had glommed more than 1 gig of physical RAM -- it's a Mac mini with 2 gigs installed.

Pretty much the only new files brought into the machine are by the web browser. Network was definitely not checked but archives may have been  checked. However, this memory use is not seen during a full scan, but just doing "on-access" scanning.   The memory is just never freed. I didn't notice this at first, but it became apparent soon.

As a result, I've had to stop the on-line scanning, but I wondered:  Is there anything I can do about it? 

I ought to note that I'm in the habit of leaving my machines on, as I use them for my home business, and they are rarely restarted.  I suppose one could kill and restart the a.v. every night via launchd. Any thoughts?

:1003247


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

    Killing and restarting the AV via launchd wouldn't work, as the AV is already self-healing (to protect against malware attempting to kill it off).  However, Intercheck should idle at around 30MB real mem, sguimenu should idle at around 2.3MB, SophosAntiVirus should idle at around 1MB, SophosAutoUpdate should idle at around 800kb, and SophosUIServer should idle at around 90MB.  SophosAVAgent should idle at around 1.3MB, and should spawn another SophosAVAgent suring a scan, that will use up CPU time and increasing real memory.  The process that should eat up more memory and CPU time during an on-access scan is Intercheck.

    Out of curiosity, do you use Google Chrome as your web browser?

    :1003249
Reply
  • 0

    Killing and restarting the AV via launchd wouldn't work, as the AV is already self-healing (to protect against malware attempting to kill it off).  However, Intercheck should idle at around 30MB real mem, sguimenu should idle at around 2.3MB, SophosAntiVirus should idle at around 1MB, SophosAutoUpdate should idle at around 800kb, and SophosUIServer should idle at around 90MB.  SophosAVAgent should idle at around 1.3MB, and should spawn another SophosAVAgent suring a scan, that will use up CPU time and increasing real memory.  The process that should eat up more memory and CPU time during an on-access scan is Intercheck.

    Out of curiosity, do you use Google Chrome as your web browser?

    :1003249
Children
No Data