Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 11 replies
  • Subscribers 1 subscriber
  • Views 6534 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 SESC9 appears to have a memory leak

VCU

Has anyone else seen this?

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

  1. Savservice.exe starts with about 94MB of memory after install.
  2. 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.
  3. 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.
  4. If checked nodes in our testing and saw savservice.exe running 200MB, 300MB and 1.2BM of memory.
  5. 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.

:2242


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

    What do others think of the following?

    I was able to test a possible solution Sophos came up with to stop the SAVservice.exe memory issue yesterday. Here is what I learned:

    I tested this possible solution and saw the following concerns:
    1. SAVservice.exe stops and is reloaded. It took 38 seconds before the reload completed. This appears to happen during each switch between update sites.   I was able to download the Eicar virus test file easily during the time SAVservice.exe was not running.

    2. The install process during the update is still taking up to 50% of the CPU.

    Results:
    The memory use issue is gone but a half minute window of no protection is provided during the switch from one update site to the next with a 50% CPU hit and no IDE or product changes provided.

    I provided this information to Sophos. I'll continue to post here information I receive concerning this issue.

    :3310
Reply
  • 0

    What do others think of the following?

    I was able to test a possible solution Sophos came up with to stop the SAVservice.exe memory issue yesterday. Here is what I learned:

    I tested this possible solution and saw the following concerns:
    1. SAVservice.exe stops and is reloaded. It took 38 seconds before the reload completed. This appears to happen during each switch between update sites.   I was able to download the Eicar virus test file easily during the time SAVservice.exe was not running.

    2. The install process during the update is still taking up to 50% of the CPU.

    Results:
    The memory use issue is gone but a half minute window of no protection is provided during the switch from one update site to the next with a 50% CPU hit and no IDE or product changes provided.

    I provided this information to Sophos. I'll continue to post here information I receive concerning this issue.

    :3310
Children
No Data
Unfiltered HTML