Private Byte Memory Leak in Rpcss.exe

 Last reviewed: August 5, 1997
Article ID: Q168260
The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.51
  • Microsoft Windows NT Server version 3.51

SYMPTOMS

Over time, the Windows NT system responsiveness appears sluggish, and clients may report a gradual decrease in system performance.

By tracking the amount of private bytes for Rpcss.exe, it can be observed that over time it increases without decreasing. This is viewable using Windows NT Performance Monitor by choosing the following counter to monitor: 

   Object:    Process
   Instance:  RPCSS
   Counter:   Private Bytes

CAUSE

A UDP remote procedure call (RPC) datagram packet was received by the server and the RPC service referenced in the packet is not running on the Windows NT server computer. During processing of the RPC datagram packet, a small buffer was allocated that was not freed.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.51. A supported fix is now available, but has not been fully regression- Tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Additional query words: prodnt
Keywords : kbbug3.51 kbfix3.51 ntnetserv NTPROTOCOL NTSrvWkst nttcp
Version : WinNT:3.51
Platform : winnt
Hardware : x86
Issue type : kbbug
Solution Type : kbfix

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: August 5, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.