Guest User!

You are not Sophos Staff.

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

Sophos is keeping close to 2 gigs of RAM inactive

MacUser59

I recently downloading Sophos on my new MacBook Pro running Lion with 8 gigs of RAM.

Since I downloaded Sophos, close to 2-3 gigs of RAM are consistently inactive in Activity Monitor. I wanted to see if anyone else has encountered this issues, and fixes (if any).

Apologies if this has been addressed elsewhere; my search didn't show the question.

Many thanks!

:1008906


This thread was automatically locked due to age.
  • 0

    I personally haven't encountered this in all my testing.  Are you currently running or have you recently run a "scan local drives" scan?  That sounds like what you'd get unpacking archives and scanning the content -- but that should be released when the scan is complete.

    :1008960
  • 0

    Hi Andrew:

    Thanks for the quick reply! I hadn't run a complete scan since I intalled Sophos a couple of weeks ago. As a test, I just ran one - didn't have time to complete the scan, but inactive RAM went from 1.40 Gigs (the amount I'm seeing if I haven't been doing to much on the Mac since I installed Sophos) to 5.39 - in essence, all the free RAM on the MacBook. When I stopped the scan, the RAM remained inactive, so I rebooted.

    Let me know if you need more information - and thanks!

    John

    :1008968
  • 0

    I'm wondering if that has something to do with memory management under Leopard -- Leopard now attempts to keep the most recent//most common items in memory and only pages out when the memory is needed by something else.  Does running something like DiskInventoryX (which also scans your entire HD) result in the memory profile changing at all?  Are you noticing any issues as a result of the inactive RAM being maxed out?

    I was going to ask if you'd quit SAV prior to checking, or just stopped the scan -- but with Lion/ML, that wouldn't really make a difference, as "quitting" no longer means "terminate process" but instead means "move down the 'must stay in memory' priority stack."  Checking active processes in Activity Monitor may shed some light however.

    Also, if you've got XCode installed, you can run the profiler to see if SAV is leaking at all, or if that's just memory that hasn't yet been reallocated.

    :1008970