timeless Reporter
	Description • 19 years ago

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.

	Chris Lawson (gone)
	Comment 1 • 19 years ago

This hangs Camino 1.0 quite nicely.

cl

	(not currently active) Ted Mielczarek
	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

	Chris Lawson (gone)
	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

	Darin Fisher
	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.

	Darin Fisher
	Comment 5 • 18 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.