RasDial( ) Leaks Resources on WinNT 4.0
Article ID: 168348
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 4.0 Standard Edition
This article was previously published under Q168348
SYMPTOMS
When an application repeatedly calls the RasDial( ) and RasHangup( ) APIs,
memory and handle leaks may be observed. One consequence of these leaks is
that Remote Access Service (RAS) can no longer dial out after a certain
number of iterations.
You may experience this problem as your Windows NT RAS client makes
repeated connections without rebooting the computer.
CAUSE
The Win32 API RAS APIs that are used for connection management do not
de-allocate all of the memory they use. Any process that repeatedly
establishes and tears down connections will cause an increased use of
memory and resources. An increase in the number of system handles used by
the process may also be observed.
RESOLUTION
Update to the latest Microsoft Windows NT 4.0 U.S. Service Pack.
STATUS
Microsoft has confirmed this to be a problem in Windows NT version 4.0.
This problem was corrected in the latest Microsoft Windows NT 4.0 U.S.
Service Pack. For information on obtaining the service pack, query on the
following word in the Microsoft Knowledge Base (without the spaces):
Keywords: kbbug KB168348