Article ID: 246691
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Server 4.0 Standard Edition
- Microsoft Windows NT 4.0 Service Pack 4
- Microsoft Windows NT 4.0 Service Pack 5
- Microsoft Windows NT 4.0 Service Pack 6
- Microsoft Windows NT Server 4.0 Enterprise Edition
- Microsoft Windows NT 4.0 Service Pack 4
- Microsoft Windows NT 4.0 Service Pack 5
- Microsoft Windows NT 4.0 Service Pack 6
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Workstation 4.0
- Microsoft Windows NT Workstation 4.0 Developer Edition
This article was previously published under Q246691
SYMPTOMS
The CreateRemoteThread application programming interface (API) may leak a handle when it is unsuccessful and return a null handle. This increases a handle count of the process that calls the CreateRemoteThread function. Because the handle is null, the calling process cannot close the handle, which results in a memory leak.
NOTE: To detect the handle leak, use Performance Monitor and monitor the Handle Count for the process that calls the CreateRemoteThread API.
CAUSE
The CreateRemoteThread function first successfully creates a thread where it creates a thread handle. If the function is unsuccessful in the later stages of processing, the created thread is terminated and the open handle to this thread is not closed. This open handle causes a memory leak.
RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Size File name Platform
-----------------------------------------------------
11/18/99 04:19pm 375,056 Kernel32.dll Intel
11/18/99 06:17pm 589,584 Kernel32.dll Alpha
STATUS
Microsoft has confirmed that this is a problem in Windows NT 4.0.
Keywords: kbbug kbfix kbqfe kbenv kbhotfixserver KB246691
