ControlService() Results in Services.exe Memory LeakLast reviewed: September 7, 1996Article ID: Q152837 |
The information in this article applies to:
SYMPTOMSApplications that repeatedly use the Win 32 call ControlService() with the SERVICE_CONTROL_INTERROGATE flag may result in a memory leak in services.exe. To identify the leak, monitor memory allocations of Services.exe using Pmon.exe, or monitor private bytes of Services.exe using performance monitor. The allocated bytes will increase abnormally over time.
CAUSEA pointer was allocated to hold the service image name that was not freed after querying the status for a driver.
STATUSMicrosoft has confirmed this to be a problem in Windows NT version 3.51. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information.
|
KBCategory: kbnetwork
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |