Closed Bug 714817 Opened 13 years ago Closed 2 years ago

No unresponsive dialog with mootools class and firebug

Categories

(Core :: JavaScript Engine, defect)

12 Branch
x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: developer, Unassigned)

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (Ubuntu; X11; Linux x86_64; rv:12.0a1) Gecko/20120103 Firefox/12.0a1
Build ID: 20120103035128

Steps to reproduce:

I have a webpage that just loops through all the items that are added to the boolean object by mootools.  It runs for a long time, freezes the browser, eats up a lot of memory, and never shows the "unresponsive dialog".  If I don't use a mootools class (so the functions are just global functions), I get the "unresponsive dialog".

You also need Firebug enabled with the script debugging turned on.

I'm attaching both the scripts.  Just click "Kill Me" to run it.
Attachment #585424 - Attachment mime type: text/plain → text/html
Attachment #585422 - Attachment mime type: text/plain → text/html
> You also need Firebug enabled with the script debugging turned on.

Chances are, this confuses the "which script is running" state so we think that it's not just one script that's running forever.
Assignee: general → nobody

Is this Bug still relevant or can it be closed by now?

Flags: needinfo?(bzbarsky)

I don't know; I didn't file this bug... That said, try running the testcases with devtools enabled and see what happens?

Flags: needinfo?(bzbarsky)
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: