Closed Bug 496847 Opened 16 years ago Closed 16 years ago

Unresponsive script alert no longer displays on Chrome infinite loop

Categories

(Core :: JavaScript Engine, defect)

1.9.1 Branch
x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED WONTFIX

People

(Reporter: morac, Unassigned)

Details

(Keywords: regression)

In the 1.9.1 branch nightlies, in a Chrome script gets into an infinite loop, the browser will hang instead of bringing up the "Unresponsive Script" alert. It doesn't matter if jit is set for chrome or not. The alert will still display on stuck browser scripts, but not chrome ones. This problem does not happen in Minefield Gecko/20090607 (nor Gecko/20090521) and presumably Tracemonkey. The easiest way to duplicate this is to type "while(1);" into the error console. It broke in the 20090521 1.9.1 branch load which gives a fairly wide number of potential causes: http://hg.mozilla.org/releases/mozilla-1.9.1/pushloghtml?startdate=may+19%2C+2009&enddate=may+21%2C+2009
Flags: blocking1.9.1?
Ah, I tried searching for something like that, but didn't look for "slow". I would have preferred just bumping up the value as there's a few extensions I have installed that can get "stuck" sometimes (Linkification tends to hang on mxr.mozilla.org). It seems like having the GUI lock up indefinitely an improvement, but whatever. At least I know how to enable it again. :) Based on the comments in bug 492410, I'll mark this WONTFIX
Status: NEW → RESOLVED
Closed: 16 years ago
Flags: blocking1.9.1?
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.