EnumServicesStatus() Results in Services.exe Memory Leak (152271)



The information in this article applies to:

  • Microsoft Windows NT Workstation 3.51
  • Microsoft Windows NT Server 3.51

This article was previously published under Q152271

SYMPTOMS

Applications that repeatedly use the Win 32 call EnumServicesStatus() may result in a memory leak in Services.exe.

CAUSE

Under certain situations a call to EnumServicesStatus() would result in Services.exe setting a heap block pointer to NULL without freeing the block first; the heap pointer that is not freed is the memory leak.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.51. This problem was corrected in the latest Windows NT 3.51 U.S. Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K


Modification Type:MajorLast Reviewed:11/3/2003
Keywords:KB152271