Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 841532 - Last Review: October 23, 2006 - Revision: 1.3
Registry handle leaks occur in applications that use MSXML DOM or XML classes after you install Microsoft Office 2003
SYMPTOMS
Applications that use the Microsoft XML Parser (MSXML) Document Object Model (DOM) or the XML classes in the Microsoft .NET Framework experience a slow and steady increase in handle usage when the applications are opening XML files from XML Web services. This problem may exhaust process resources and cause an error or an out-of-memory condition. The program must be restarted to reclaim the lost handles. This problem occurs on computers that have Microsoft Office 2003 installed. The problem does not occur on computers that have earlier versions of Microsoft Office installed.
CAUSE
This problem is caused by a leak of registry key handles in a client-side MIME protocol filter for XML files that are returned from XML Web services. The Microsoft Office XML MIME filter (Msoxmlmf.dll) is a registered MIME protocol handler. Msoxmlmf.dll can load indirectly in any application that uses the MSXML to parse XML data from an XML Web service. The filter is used by the Wininet library component and the Urlmon library component to identify XML files that are associated with Office 2003. One registry key handle is leaked every time that the filter object is created. The filter object is typically created one time per session. However, services that destroy and re-create repeated XMLHttpRequest objects and that parse the resulting XML may experience conditions that cause a new session to be created for every request. When a new session is created for every request, a slow leak of registry key handles occurs.
WORKAROUND
Clients can remove the filter to avoid the leak if the problem is so serious that it causes application errors in other processes. To remove the filter, follow these steps:
- Verify that the Msoxmlmf.dll filter is installed in the Office shared folder. The following is the default location for this folder:
C:\Program Files\Common Files\Microsoft Shared\Office11\Msoxmlmf.dll
- Click Start, click Run, type regsvr32.exe /u "c:\program files\common files\microsoft shared\office11\msoxmlmf.dll", and then click OK.
If the Msoxmlmf.dll filter is installed in a location that is not the default location, type the path of the actual location of the filter.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
The Microsoft Office XML MIME Filter (Msoxmlmf.dll) is registered under the following registry key:
HKEY_CLASSES_ROOT\Protocols\Filter\text/xml
Removing this key also prevents the filter from loading in a custom application.
APPLIES TO
- Microsoft Office Professional Edition 2003
- Microsoft XML Core Services 4.0
- Microsoft .NET Framework 1.0
| kbbug kbnofix kbxml KB841532 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please