Article ID: 321621
Article Last Modified on 11/15/2007
APPLIES TO
- Microsoft XML Parser 3.0 Service Pack 2
- Microsoft XML Core Services 4.0 Service Pack 1
This article was previously published under Q321621
SYMPTOMS
Your application may quit if the following conditions are true:
- You load an XML document repeatedly.
- You release the IXMLDOMDocument interface pointer.
- The application is multithreaded and uses MSXML2.FreeThreadedDOMDomcument30 or MSXML2.FreeThreadedDOMDomcument40.
- The application forces memory allocation in the high memory range (between 2 GB and 3 GB).
If your application quits, you may receive an access violation with one of the following error messages:
-or-
NOTE: You must compile an application that is written in Microsoft Visual C++ with the /LARGEADDRESSAWARE switch if the application must use a memory address space that is larger than 2 GB.
CAUSE
The MSXML parser uses the pointer cache to manage objects for garbage collection. The pointer cache does not account for values greater than 2 GB.
RESOLUTION
MSXML 4.0
A supported hotfix is now 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
The English version of this fix 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 ------------------------------------------------------------------ 26-Apr-2002 5:36:55 PM 4.0.9626.0 1,227,776 bytes Msxml4.dll 26-Apr-2002 5:36:55 PM 4.0.9626.0 44,544 bytes Msxml4a.dll 26-Apr-2002 5:36:55 PM 4.0.9626.0 82,432 bytes Msxml4r.dll
MSXML 3.0
A supported hotfix is now 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
The English version of this fix 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 ------------------------------------------------------------------ 03-May-2002 5:36:55 PM 8.20.9703.0 1,120,768 bytes Msxml3.dll
WORKAROUND
To work around this issue, use either of the following methods:
- In the Boot.ini file, remove the /3GB switch that is used to enable 4GT Tuning. -or-
- Disable full garbage collection (FullGC) by setting NoFullGC to 1 in the registry.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
REFERENCES
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
Keywords: kbhotfixserver kbqfe kbbug kberrmsg kbfix kbfix kbqfe KB321621