403999 - alert() called from deeply nested js function is blank and cannot be closed

Status: NEW

(Core :: DOM: Core & HTML, defect, P5)

Description

[Jesse Ruderman]

Attachment: testcase (essentially hangs Firefox when loaded)

This was reported at 
http://www.thespanner.co.uk/2007/11/14/firefox-history-dos-attack/ (which reed pointed me to).  It's also part of what goes wrong in bug 246377.

Note that the testcase here is clearer than the testcase on thespanner.co.uk.

Comment 1

[Jesse Ruderman]

Attachment: testcase (essentially hangs Firefox when loaded)

Comment 2

[Jesse Ruderman]

CCing people from bug 339652, since they know about the too-much-recursion checks in dom/ and js/src/.  (This was initially found on branch, but still happens on trunk, so I guess the fix for that bug didn't change the behavior here.)

Comment 3

[Biju]

Pressing escape key will close it.
But underneath you will see another. and another and so on.
Finally you will start seeing a good alert boxes.  

Comment 4

[Ryan VanderMeulen [:RyanVM]]

This testcase crashes for me after a brief hang.

Comment 5

[Luke Wagner [:luke]]

I see the slow-script dialog (mangled it may be) so I'll lob this over to DOM.

Comment 6

[Boris Zbarsky [:bzbarsky]]

Isn't this just a matter of running out of JS stack while trying to run the UI JS?  I don't think there's anything the DOM per se can do about that....

Comment 7

[Luke Wagner [:luke]]

DOM gets the DOMOperationCallback, so, even if JS does run out of stack, I think execution should be halted.  Due to the nesting, I suspect this is related to bug 726174, which needs attention from a DOM-knowing person.

Comment 8

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.