Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 818625 - Last Review: December 2, 2003 - Revision: 1.0
XML May Stop Responding When You Make a Change to the Nodes of an FTDOMDoument on a Multiprocessor or a Hyper-Threaded Computer
You may experience a deadlock in MSXML 4.0 or MSXML 4.0 Service Pack 1 (SP1) under stress while you make a change to the nodes of an XML free-threaded Document Object Model (DOM) document. This problem becomes evident when several threads are blocked on a semaphore object and your computer stops responding.
This problem is caused by overly pessimistic locking in the document locking code in MSXML.
This problem was corrected in MSXML 4.0 Service Pack 2.
There is no workaround for this problem.
APPLIES TO
- Microsoft XML Core Services 4.0
- Microsoft XML Core Services 4.0 Service Pack 1
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