Sophos SESC9 appears to have a memory leak

I have posted this again because my earlier post was closed before I received a solution.

Here is an update on this:

Sophos confirmed there have been defects seen for the issues I reported under:

2##### : In regards to the CPU usage / memory leakage
2##### : In regards to the unknown up-to-date status

The Sophos engineer that worked on the cases with me stated "I suspect they will be fixed in the next maintenance release, roughly within one months’’’’ time. However I’’’’ll be monitoring the progress of the fix and let you know when to expect it."

I'll up date this post once I see things resolved.

Issue and history:------------------------------------------

Thu 01-Apr-2010 15:24

Sophos SESC9 appears to have a memory leak

Has anyone else seen this?

 I've been testing SESC9 for a few months and found the following:

Savservice.exe starts with about 94MB of memory after install.
Our managed nodes are setup to fail over to Sophos for updates if they can not reach our sites. When this occurs the Sophos site installs 1 of 1 and savservice.exe increases in memory use.
This same thing occurs when our node comes back to update from our site install 1 of 1 and savservice.exe increases in memory use.
If checked nodes in our testing and saw savservice.exe running 200MB, 300MB and 1.2BM of memory.
I tested this on my computer and watched savservice.exe go from 94MB to 140MB before stopping my test.
 

I look forward to seeing what you have experienced.

Fri 09-Apr-2010 15:13

Here is an update on my post.

I've worked with Sophos tech support under two separate cases. Both have been escalated to global support. I also have a Sophos engineer that confirmed he saw the same thing in his testing. He will be overseeing the status of my cases.

When I hear back on their status I'll post it here.

Thanks

I have posted this again because my earlier post was closed before I received a solution.

Here is an update on this:

Sophos confirmed there have been defects seen for the issues I reported under:

2##### : In regards to the CPU usage / memory leakage
2##### : In regards to the unknown up-to-date status

The Sophos engineer that worked on the cases with me stated "I suspect they will be fixed in the next maintenance release, roughly within one months’’’’ time. However I’’’’ll be monitoring the progress of the fix and let you know when to expect it."

I'll up date this post once I see things resolved.

Issue and history:------------------------------------------

Thu 01-Apr-2010 15:24

Sophos SESC9 appears to have a memory leak

Has anyone else seen this?

 I've been testing SESC9 for a few months and found the following:

Savservice.exe starts with about 94MB of memory after install.
Our managed nodes are setup to fail over to Sophos for updates if they can not reach our sites. When this occurs the Sophos site installs 1 of 1 and savservice.exe increases in memory use.
This same thing occurs when our node comes back to update from our site install 1 of 1 and savservice.exe increases in memory use.
If checked nodes in our testing and saw savservice.exe running 200MB, 300MB and 1.2BM of memory.
I tested this on my computer and watched savservice.exe go from 94MB to 140MB before stopping my test.
 

I look forward to seeing what you have experienced.

Fri 09-Apr-2010 15:13

Here is an update on my post.

I've worked with Sophos tech support under two separate cases. Both have been escalated to global support. I also have a Sophos engineer that confirmed he saw the same thing in his testing. He will be overseeing the status of my cases.

When I hear back on their status I'll post it here.

Thanks