Closed Bug 330771 Opened 14 years ago Closed 6 months ago

xmldocument.nsIDOMXMLDocument.load (sync) can hang browser

Categories

(Core :: XML, defect, major)

defect
Not set
major

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: timeless, Unassigned)

References

(Depends on 1 open bug, )

Details

(Keywords: hang)

this is from a customer's site.
mozilla branch: 1.8 (details unknown)
internal build: 1851

steps to reproduce:
1. load
http://viper.haque.net/~timeless/blog/index.xml
2. load
javascript:x=document.implementation.createDocument("http://www.w3.org/2000/xmlns/","",null); x.async = false; throw x.load("http://viper.haque.net")

expected results:
no idea

actual results:
browser is hung

note: it is possible to unhang your browser if you have a debugger (symbols are optional but kinda helpful). all you have to do is poke nsXMLDocument.mLoopingForSyncLoad back to false.
This hangs Camino 1.0 quite nicely.

cl
Hangs my trunk build on XP as well.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060315 Firefox/1.6a1
OS: Windows XP → All
Hardware: PC → All
Version: 1.8 Branch → Trunk
Though Ted just assigned this to "Trunk", it's worth mentioning that it affects the 1.8 branch as well (Camino 1.0).

cl
Depends on: nsIThreadManager
With a build from THREADS_20060307_BRANCH, I cannot reproduce this bug.  With a trunk build, I see this bug.  So, I'm pretty sure that my patch for bug 326273 will help with this bug.
This is not fixed by my patch for bug 326273.  While it avoids hanging the browser complete (the UI remains responsive), the browser is left unable to shutdown.  A stack trace reveals that the browser is stuck in the load loop waiting for the resource to finish loading.  I'm surprised that the network channel is not being killed by app shutdown.
Assignee: xml → nobody
QA Contact: ashshbhatt → xml
Depends on: 983090

XMLDocument.load has been removed in bug 332175.

Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.