330293 - Firefox Gives "Warning: Unresponsive Script" and Hangs on Most Pages With JS

Status: RESOLVED DUPLICATE of bug 335058

(Firefox :: General, defect)

Description

[Ty Williams]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

NOTE: This was noticed after upgrading from a PowerBook G4 to a MacBook Pro.  Both systems were running Firefox 1.5.0.1.  No way for me to go back and see if this problem happens on the old hardware too.

When Firefox encounters just about any page with JavaScript, it will hang for about 5 seconds or so at 100% CPU usage and then return the "Warning: Unresponsive Script" dialog box.  Clicking "Continue" will result in repeating the hang-warning cycle.  Clicking "Stop Script" will return things to normal.  Disabling JS in the preferences will cause this error behavior to stop.

For a 100% guarnteed test case, visit any of the pages about individual tires on http://www.tirerack.com/

Reproducible: Always

Steps to Reproduce:
1. Open Firefox
2. Navigate to a JS-heavy page such as the individual tire descriptions on http://www.tirerack.com/

Actual Results:  
Firefox will go to 100% CPU usage and become unresponsive for around 5 seconds.  It will then display the "Warning: Unresponsive Script" dialog box.

Expected Results:  
Firefox should load the page and execute the JS without drama.

This is possibly a dupe of bugs 320409, 320020, and/or others found using the search string "unresponsive script". However, all those other bugs have different sites triggering them, so I'm putting this up.

Comment 1

[Ria Klaassen (not reading all bugmail)]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
I don't see that. But possibly if you double the value of dom.max_script_run_time in about:config it will help.
http://kb.mozillazine.org/About:config

Comment 2

[Jo Hermans]

*** This bug has been marked as a duplicate of 335058 ***