Closed
Bug 330771
Opened 19 years ago
Closed 5 years ago
xmldocument.nsIDOMXMLDocument.load (sync) can hang browser
Categories
(Core :: XML, defect)
Core
XML
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: timeless, Unassigned)
References
()
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.
Comment 1•19 years ago
|
||
This hangs Camino 1.0 quite nicely.
cl
Comment 2•19 years ago
|
||
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
Updated•19 years ago
|
OS: Windows XP → All
Hardware: PC → All
Version: 1.8 Branch → Trunk
Comment 3•19 years ago
|
||
Though Ted just assigned this to "Trunk", it's worth mentioning that it affects the 1.8 branch as well (Camino 1.0).
cl
Updated•19 years ago
|
Depends on: nsIThreadManager
Comment 4•19 years ago
|
||
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.
Comment 5•19 years ago
|
||
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.
Updated•15 years ago
|
Assignee: xml → nobody
QA Contact: ashshbhatt → xml
Comment 6•5 years ago
|
||
XMLDocument.load has been removed in bug 332175.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•