Microsoft COM+ applications that do not call the Dispose
method on all instances of the ServicedComponent
in the Microsoft .NET Framework versions 1.1 and 1.0 may experience slow
performance, deadlocks, and memory leaks.
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 Microsoft .NET Framework 1.1 or 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 file attributes) 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 item in Control Panel.
Date Time Version Size File name
19-Nov-2004 13:27 1.0.3705.556 11,264 Regsvcs.exe
19-Nov-2004 13:27 1.0.3705.556 212,992 System.enterpriseservices.dll
18-Nov-2004 05:40 1.0.3705.556 48,640 System.enterpriseservices.thunk.dll
Microsoft has confirmed that this is a bug in the Microsoft products that are
listed in the "Applies to" section.
This hotfix changes the behavior of the asynchronous
finalization of ServicedComponent
objects to avoid the symptoms that are described in the
"Symptoms" section. The DisableAsyncFinalization registry entry
can be used as a temporary workaround only for deadlocks. However, this
workaround may worsen the other symptoms of slow performance and memory leaks.
The correct approach is the systematic use of the Dispose
method by the client of the ServicedComponent
objects on all instances of the ServicedComponent
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
FIX: A COM+ application that uses the global interface table (GIT) may deadlock