SNMP Leaks Memory If the OID Cannot Be Decoded

This article was previously published under Q178381
This article has been archived. It is offered "as is" and will no longer be updated.
Over time, the Windows NT system responsiveness appears sluggish, andClients may report a gradual decrease in system performance.

By tracking the amount of Private Bytes for Snmp.exe, it can be observedthat, over time, it increases without decreasing. This is viewable usingWindows NT Performance Monitor by selecting the following counter tomonitor:

Object: Process
Instance: SNMP
Counter: Private Bytes
If SNMP cannot decode an OID from a network packet, SNMP does not free upthe memory, resulting in a memory leak in the Snmp.exe processes. Theimpact of this leak will be more evident on a system running on a networksegment that receive lots of SNMP broadcast traffic.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

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 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
SNMP debug

Article ID: 178381 - Last Review: 10/07/2013 16:18:37 - Revision: 2.2

Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbapi kbbug kbfix kbnetwork kbqfe kbsnmp KB178381