Memory Leak in Programs That Load/Unload Security.dll (238493)

SYMPTOMS

A program may exhibit a memory leak if the program causes Security.dll to be loaded and unloaded repeatedly while the process is running. You can observe the memory leak by using Windows NT Performance Monitor to track Private Bytes for the program process.

An example of a program that can exhibit this problem is an SNA program running on a Windows NT client using the SNA Server Client for Windows NT. Each time the SNA program (or process) initiates a new host session, the underlying SNA Server client causes Security.dll to be loaded to perform Windows NT user validation to determine if the user is authorized to gain access to SNA Server.

Over time, a computer may stop responding (hang) if a process experiencing this problem is left running long enough to exhaust the system's memory resources.

CAUSE

Security.dll creates a critical section when it attaches to a process that causes it to be loaded. This critical section is not deleted when Security.dll detaches from the process when it is unloaded, which causes the memory leak.

RESOLUTION

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

http://www.microsoft.com/windows/servicepacks/ -or-
152734how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/directory/overview.asp

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack

STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition.

This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.