Closed
Bug 715080
Opened 13 years ago
Closed 13 years ago
Infinite recursion cannot be stopped with "Unresponsive Script Warning" function
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 682793
People
(Reporter: mynthon1, Unassigned)
Details
Attachments
(1 file)
333 bytes,
text/html
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 Build ID: 20111220165912 Steps to reproduce: Infinite recursion in javascript (see attached file - save for open). Firefox 9.0.1, Windows 7 Proffesional SP1, 64-bit. Actual results: "Unresponsive Script Warning" alert pops up but clicking "Stop script" doesn't stops script. Script is still running. Expected results: In google chrome i get "Uncaught RangeError: Maximum call stack size exceeded" and it would be the best option, but at least "Stop script" button should break scripts on page.
Updated•13 years ago
|
Attachment #585683 -
Attachment mime type: text/plain → text/html
Comment 1•13 years ago
|
||
On Mac I get "Error: too much recursion" on the error console on both 8.0.1 and 9.0.1 -- I don't see the described behavior at all. Hard to imagine this behavior being platform dependent but will test Windows when I get a chance.
Assignee: nobody → general
Component: General → JavaScript Engine
Product: Firefox → Core
QA Contact: general → general
Comment 2•13 years ago
|
||
Reporter, do you have Firebug installed?
Reporter | ||
Comment 3•13 years ago
|
||
yes, i do. On Nightly 12.0a1 without firebug i get error: too much recursion. So this is firebug fault?
Reporter | ||
Comment 4•13 years ago
|
||
Ok, did some more testing and you are right. This is caused by firebug. With Firebug disabled i get "too much recursion" in evry firefox version.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Comment 5•13 years ago
|
||
Yeah, there's a known issue with Firebug where it will try to do some sort of handling on the "too much recursion" exceptions, but that processing tries to use the stack, which is full, so throws that same exception again and round Firebug goes.... There are existing bugs on this.
Group: core-security
Updated•12 years ago
|
Resolution: INVALID → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•