Start a Conversation

Unsolved

This post is more than 5 years old

134599

January 30th, 2014 01:00

OMCI memory leak on Windows 8.1?

I am running OMCI across our desktop fleet and have begun encountering resource exhaustion on some of our workstations after upgrading to Windows 8.1. I first saw the problem on OMCI 8.2.0, and have already upgraded to 8.2.1 which according to the release notes is supported on Windows 8.1. I have not yet encountered the problem on Windows 7.

So far the affected machines have been older OptiPlex 380 workstations (Core 2 Duo E7400, 3GB RAM, BIOS A07). Users typically report the problem after returning to it while it has been left idle. The machine is unresponsive to user input and the monitor does not come out of power save, but the machine responds to PING and is available for remote RPC management.

The telltale sign is that Windows logs events as per the following:

Log Name: System
Source: Microsoft-Windows-Resource-Exhaustion-Detector
Date: 30/01/2014 02:28:20
Event ID: 2004
Task Category: Resource Exhaustion Diagnosis Events
Level: Warning
Keywords: Events related to exhaustion of system commit limit (virtual memory).
User: SYSTEM
Computer: Cello.crosfields.internal
Description:
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: dsm_sa_datamgr32.exe (1448) consumed 1232412672 bytes, SBAMSvc.exe (3312) consumed 106643456 bytes, and svchost.exe (960) consumed 46395392 bytes.

As you can see, the dsm_sa_datamgr32.exe is consuming more than 1GB of RAM at this point. Idle memory usage for this process is normally less than 10MB on our workstations according to the task manager. These messages typically go back a couple of days; in the above case, the first message was logged 28 hours previous when the dsm_sa_datamgr32.exe was consuming 263MB of RAM, and interim messages show that number steadily increasing over the next day.

Is there anything I can do to aid further diagnosis of this issue? 

January 30th, 2014 01:00

Can you provide the details of the monitor used? Also can you confirm if this issue is reproduce when the monitor doesn't move into standby mode individually and so also for the system. We have noticed similar issue with a P2010H and P2011H monitor which is fixed and the next release of OMCI will have the fix integrated.

January 30th, 2014 01:00

Thanks for the reply. I don't have any cases logged yet where the system and monitor had not been in standby. Each case is using the same monitor so far - the ST2220T, connected via DVI. We do have a bank of machines with the P2010H that I am planning to upgrade to Windows 8.1 in a couple of weeks. Is the fix likely to be available by then?

February 2nd, 2014 19:00

The tentative plan for the delivery of the next release of OMCI is arround Q2-Q3 CY'14.

February 3rd, 2014 00:00

OK thanks, that's useful to know. I will hold off deploying OMCI on Windows 8 for now and revisit once the new release is available.

September 8th, 2014 05:00

Hi All,

We have worked on a fix with Dell Command | Monitor v9.0 (rebranded name for OMCI). Request you to kindly update your results with the latest release

No Events found!

Top