Microsoft Knowledge Base Email Alertz

KBAlertz.com: (824192) - When you make a change to an XML node directly in an XMLHTTP application, you receive the following general protection fault (GP fault) error message: The instruction at memoryaddress referenced memory at memoryaddress . The memory could not be...

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **


Community Site



We Send hundreds of thousands of emails using ASP.NET Email


ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 824192 - Last Review: March 13, 2004 - Revision: 1.1

BUG: General protection fault when you make changes to XML nodes

SYMPTOMS

When you make a change to an XML node directly in an XMLHTTP application, you receive the following general protection fault (GP fault) error message:
The instruction at <memoryaddress> referenced memory at <memoryaddress>. The memory could not be "read".
Note<memoryaddress> is the placeholder for the respective memory address.

CAUSE

When an event is raised in an XMLHTTP application, the Mshtml.dll file may destroy a node to replace the node during XML node manipulation in the event handler. Other statements may exist in the event handler in an Internet Explorer message loop that may access the XML node directly for manipulation. When the node is accessed directly, a GP fault occurs because it accesses a node that no longer exists. The node was moved by the Mshtml.dll file.

WORKAROUND

To work around this problem, avoid direct access of the node in the event handler, and include a process timer to fire the manipulation code after a short delay of 100 milliseconds.

For example, if the original call that changes the nodes is the MoveNode(item) function, create a worker function that is named MoveNode_Worker(item), and then move the code that actually handles the manipulation of the nodes to the MoveNode_Worker(item) function. In the MoveNode() function, call the MoveNode_Worker(item) worker thread after 100 milliseconds by using the window.setInterval() function function.
interval = window.setInterval("MoveNode_Worker(item)",100);

STATUS

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

REFERENCES

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
288913  (http://kbalertz.com/Feedback.aspx?kbNumber=288913/ ) HOWTO: Use XPath queries in MSXML DOM selectNodes method

APPLIES TO
  • Microsoft Internet Explorer (Programming) 6 (SP1)
  • Microsoft XML Parser 2.0
  • Microsoft XML Parser 2.5
  • Microsoft XML Parser 2.6
  • Microsoft XML Parser 3.0
  • Microsoft XML Core Services 4.0
Keywords: 
kbhtml kbxml kbbug KB824192
       

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

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please