FIX: Marshal.ReleaseComObject Does Not Correctly Release Objects That Implement the IDisposable Interface

Article translations Article translations
Article ID: 826915 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all


If events are used from managed code, the Marshal.ReleaseComObject method does not correctly release a COM object that implements the IDisposable interface.


A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next .NET Framework 1.0 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date         Time   Version       Size       File name
12-Aug-2003  12:17  1.0.3705.449    200,704  Aspnet_isapi.dll
12-Aug-2003  12:11                    4,169  Aspnet_perf.h
12-Aug-2003  12:18                  513,302  Aspnet_perf.ini
12-Aug-2003  12:18                  510,714  Aspnet_perf2.ini
12-Aug-2003  12:18  1.0.3705.449     24,576  Aspnet_regiis.exe
12-Aug-2003  12:18  1.0.3705.449     28,672  Aspnet_wp.exe
12-Aug-2003  11:40  1.0.3705.449     69,632  Corperfmonext.dll
12-Aug-2003  11:30  1.0.3705.449  1,953,792  Mscorlib.dll
12-Aug-2003  11:31                   10,284  Mscorlib.ldo
12-Aug-2003  11:39  1.0.3705.449  2,269,184  Mscorsvr.dll
12-Aug-2003  11:39  1.0.3705.449  2,269,184  Mscorwks.dll
01-Aug-2002  17:38                       15  Smartnav.htm
29-Jul-2003  16:30                    8,728  Smartnav.js
12-Aug-2003  12:27  1.0.3705.449  1,196,032  System.web.dll


Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

More information

This problem prevents the COM object from being released correctly. When the COM object is not released correctly, memory usage grows. Also, semantic problems may occur. For example, some object models will not quit unless all the references are released.

To work around this problem, you can do a full garbage collection to deterministically release the COM objects. However, this method significantly decreases performance.


Article ID: 826915 - Last Review: October 26, 2013 - Revision: 3.0
Applies to
  • Microsoft .NET Framework 1.0
kbnosurvey kbarchive kbhotfixserver kbqfe kbnetframe100presp3fix kbfix kbbug KB826915

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from