Applications leak memory when creating COM objects by calling the CoCreateInstance function with a CLSID that is not valid on computers that are running Windows 2000 SP4 (827711)
The information in this article applies to:
- Microsoft COM+ 1.0, when used with:
- the operating system: Microsoft Windows 2000 SP4
SYMPTOMSAfter you apply Microsoft Windows 2000 Service Pack 4, if
certain errors (such as invalid class identifiers (CLSIDs)) occur when applications try to create
Component Object Model (COM) objects, the applications start to leak memory.
The applications typically create COM objects by using the CoCreateInstance function. Analysis of the leaked memory shows environment
variable strings.CAUSEDuring successful object creation, COM calls the GetEnvironmentStrings function and then calls the corresponding FreeEnvironmentStrings function. However, in certain error conditions (such as when the
CLSID is not valid), COM does not call the FreeEnvironmentStrings function. Before Windows 2000 Service Pack 4, this was not a
problem. With Windows 2000 Service Pack 4 or later, this causes a memory leak.
With this hotfix applied, COM correctly calls the FreeEnvironmentStrings function even in error cases.RESOLUTIONHow to obtain the hotfixThis issue is fixed in the Microsoft COM+ 1.0 Hotfix Package 28. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 828748 Availability of Windows 2000 Post-Service Pack 4 COM+ Hotfix Rollup Package 28 STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
| Modification Type: | Major | Last Reviewed: | 1/25/2005 |
|---|
| Keywords: | kbWin2000preSP5fix kbfix kbBug KB827711 kbAudDeveloper |
|---|
|