Memory Leak on Clients with Remote Procedure Calls
PSS ID Number: 128353
Article Last Modified on 11/4/2003
The information in this article applies to:
- Microsoft Windows NT Workstation 3.5
- Microsoft Windows NT Server 3.5
This article was previously published under Q128353
SYMPTOMS
After the client side of Remote Procedure Call (RPC) creates large number
of threads, makes an RPC, and exits, a memory leak occurs. The server side
of the RPC is not affected.
CAUSE
When the client side of RPC thread disappears, the thread pointer in the
TLS storage is not released.
STATUS
Microsoft has confirmed this to be a problem in Windows NT version 3.5. A
fix to this problem is in development, but has not been regression-tested
and may be destabilizing in production environments. Microsoft does not
recommend implementing this fix at this time. Contact Microsoft Product
Support Services for more information on the availability of this fix.
Additional query words: prodnt
Keywords: KB128353
Technology: kbWinNT350search kbWinNTS350 kbWinNTS350search kbWinNTsearch kbWinNTSsearch kbWinNTW350 kbWinNTW350search kbWinNTWsearch