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

NEW
Unassigned

Status

()

Core
DOM
10 years ago
4 years ago

People

(Reporter: Jesse Ruderman, Unassigned)

Tracking

({crash, hang, testcase})

Trunk
crash, hang, testcase
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: js-triage-needed, URL)

Attachments

(1 attachment, 1 obsolete attachment)

(Reporter)

Description

10 years ago
Created attachment 288948 [details]
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.
(Reporter)

Updated

10 years ago
Blocks: 246377
(Reporter)

Comment 1

10 years ago
Created attachment 288949 [details]
testcase (essentially hangs Firefox when loaded)
Attachment #288948 - Attachment is obsolete: true
(Reporter)

Comment 2

10 years ago
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

10 years ago
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.  
This testcase crashes for me after a brief hang.
OS: Mac OS X → All
Hardware: x86 → All
Keywords: crash
Whiteboard: js-triage-needed

Comment 5

6 years ago
I see the slow-script dialog (mangled it may be) so I'll lob this over to DOM.
Assignee: general → nobody
Component: JavaScript Engine → DOM
QA Contact: general → general
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....
(Reporter)

Updated

6 years ago
Depends on: 732665

Comment 7

6 years ago
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.
You need to log in before you can comment on or make changes to this bug.