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

Sophos is keeping close to 2 gigs of RAM inactive

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.
Parents
  • 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
Reply
  • 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
Children
No Data