706911 - Page causes 100% CPU usage and "Stop script" in unresponsive script dialog only works once

Status: RESOLVED DUPLICATE of bug 702572

(Core :: JavaScript Engine, defect)

Description

[Frank Wein [:mcsmurf]]

Warning, the following steps to reproduce will likely get Firefox in a state where you need to force quit it.
Steps to reproduce:
1. Go to URL
2. Watch Firefox consume 100% CPU, wait for unresponsive script dialog to appear and click on "Stop script"
3. Watch Firefox recover and wait a bit for Firefox to consume 100% CPU again
4. Now you should get the unresponsive script dialog again, but this time the "Stop script" button does not seem to work anymore; you can click on "Stop script", Firefox will not recover. You should get the unresponsive script dialog again and again, the "Stop script" button will not work anymore

Probably this bug should go to Core-JS Engine, but not sure about that.

Comment 1

[Frank Wein [:mcsmurf]]

Maybe related: Bug 640471 (in that bug there's no unresponsive script dialog at all though)

Comment 2

[Frank Wein [:mcsmurf]]

Probably belongs in JS Engine component.
Possibly related: Bug 574616, maybe this bug here is the same problem as mentioned in Bug 574616 Comment 1, origin tracking being broken. Though this bug here is a bit different as the first time the the "Stop script" button works, but after that it does not.

Comment 3

[Frank Wein [:mcsmurf]]

(In reply to Frank Wein [:mcsmurf] from comment #0)
For the second, third, ... unresponsive script dialog to happen you need to actually select some text on that webpage. Not sure why, but that's the way it is.

BTW: This is a regression, it regressed between http://hg.mozilla.org/mozilla-central/rev/322354df233d and http://hg.mozilla.org/mozilla-central/rev/dfbe9a0fbf97 (2011-10-28-03-10-44-mozilla-central and 2011-10-29-03-10-36-mozilla-central)

Comment 4

[Frank Wein [:mcsmurf]]

Bug 706972 looks like it's the same, let's use that one for now.

Comment 6

[Boris Zbarsky [:bzbarsky]]

A minimized testcase would be really nice.

The range is http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=322354df233d&tochange=dfbe9a0fbf97 which doesn't seem to have anything obviously relevant...

Comment 7

[Alice0775 White]

About regression range of 100% CPU usage , Pls See Bug 706972

Comment 8

[Frank Wein [:mcsmurf]]

The slow script warning says something about prototype.js and Bug 702572 also talks about prototype.js (Bug 702572 has been caused by Bug 684489). So possibly that bug/patch will fix this bug here, too. A developer probably needs to comment on this if that will be true or not.

Comment 9

[Frank Wein [:mcsmurf]]

Tested locally, the patch from Bug 702572 fixes this bug here, too.

Comment 11

[Asa Dotzler [:asa]]

unsetting the tracking request because duplicate. re-nominate if that's wrong.