FIX: You may experience an increase in memory usage in an application that uses XML Core Services 6.0

You may experience an increase in memory usage in an application that uses Microsoft XML Core Services 6.0 (MSXML6).

The increased memory usage occurs because of an increase in document and semaphore handle counts.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

File information

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.

XML Core Services, x86-based versions

XML Core Services, Itanium-based versions

XML Core Services, x64-based versions

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

This issue occurs because of a mismatch in the AddRef and Release counts in the MSXML6 node locking code. The mismatch in the AddRef and Release counts may cause a document to be released incorrectly. When the document is released incorrectly, an access violation may occur. However, the primary symptom may be a large increase in memory usage that is followed by a slower increase in memory usage.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: