Memory Leak in RPC When Doing Repeated Binding Lookups

This article was previously published under Q219332
This article has been archived. It is offered "as is" and will no longer be updated.
When you run repeated RPC NSBinding Lookups to see what services are bound to RPC, an increasing amount of memory is used, which causes a memory leak.
This problem occurs because of a failure to issue a "delete EntryName;" call in BINDING_HANDLE::~BINDING_HANDLE
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:
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:
Microsoft has confirmed that this is a problem in Windows NT Server 4.0. This problem was first corrected in Windows NT version 4.0 Service Pack 5.

Article ID: 219332 - Last Review: 11/03/2013 00:01:00 - Revision: 3.0

Microsoft Windows NT Server 4.0 Standard Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB219332