BUG: SNMP Extended Stored Procedures May Leak Memory

ID: Q234679

The information in this article applies to:
BUG #: 18732 (SQLBUG_65)

SYMPTOMS

If Simple Network Management Protocol (SNMP) integration is enabled and any of the SNMP-related extended stored procedures are run, you may see a handle and memory leak within the SQL Server address space. The leak is characterized by an increase of four handles and 8 KB of virtual bytes for each invocation of one of the extended stored procedures.


RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. 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:

http://www.microsoft.com/support/supportnet/overview/overview.asp
The English version of this fix should have the following file attributes or later: 

   Version       File name        Platform
   ---------------------------------------

   6.50.441      Sql441i.exe      Intel
   6.50.441      Sql441a.exe      Alpha
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5.


MORE INFORMATION

SQL Server SNMP integration is provided by Sqlsnmp.dll. This module contains two different extended stored procedures, xp_snmp_getstate and xp_snmp_raisetrap.

The memory leak actually leads to a fragmented virtual address space and may cause SQL Server to stop responding. For additional information, please see the following article in the Microsoft Knowledge Base:

Q216381 BUG: Error Spawning Thread Not Handled Correctly by SQL & ODS

Additional query words: xproc 17802 smnp hang hangs hung 


Keywords          : SSrvAdmin SSrvGen kbbug6.50 
Version           : winnt:6.5
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: July 2, 1999