Closed
Bug 552406
Opened 14 years ago
Closed 14 years ago
Jquery-1.2.6.js:11 script is not responding and causes firefox to hang (not responding)
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
DUPLICATE
of bug 607856
Tracking | Status | |
---|---|---|
blocking2.0 | --- | betaN+ |
People
(Reporter: dominique, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2) Gecko/20100115 Firefox/3.6 GTBDFff GTB7.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2) Gecko/20100115 Firefox/3.6 GTBDFff GTB7.0 Nothing more to do than go on this website: www.comparance.com. There is a script (jquery-1.2.6.js:11) on the home page that causes Firefox to hang and not to respond anymore. It's not instantaneous, it does take a while to happen. Older versions of Firefox never caused that bug as I have been on this website many times before. Believe it or not ! but IE works perfect… It’s really related to this version of Firefox It happens after a few minutes mostly when I come back and the screeensaver is on... Reproducible: Always Steps to Reproduce: 1.Go a the web site 2.Let the tab open and see what happens 3.Go out for lunch and get back later if needed Actual Results: Just hangs and have to CTR-ALT-Delete to restart firefox
The web site was www.comparance.com Now I get another script error when I refresh the page : Script: chrome://firebug/content/tabWatcher.js:517
Now it bugs on GMAIL : Script:https://mail.google.com/mail/?ui=2&name=js&ver=Y12kZ5.....
Comment 4•14 years ago
|
||
I can also reproduce this problem on this website, with Firefox 4.0b7 (but not with Fx 3.6.12): http://www.esep.ch/web/ When you click the "Documents à télécharger" link in the left menu (sometimes, you have to click on another link first to trigger the hang), you get a popup that Firefox hangs on: Script : http://www.esep.ch/web/sites/default/files/js/js_f28f52e815bb8955477d3c15cc10bde9.js:13 which is the exact same file and line as the one reported in comment 0 (except that the one on esep.ch has an additional comment at line 1). bz, could this be related to bug 614164?
Assignee: nobody → general
Status: UNCONFIRMED → NEW
blocking2.0: --- → ?
Component: General → JavaScript Engine
Ever confirmed: true
OS: Windows 7 → All
Product: Firefox → Core
QA Contact: general → general
Hardware: x86_64 → All
Version: unspecified → Trunk
Comment 5•14 years ago
|
||
Also, note that Opera and Chrome do not hang, and are fast to display the page.
Comment 6•14 years ago
|
||
> bz, could this be related to bug 614164?
No. That bug is about executing jquery stuff of various sorts that does run but runs about 2x slower than other browsers, not pathologically slower.
Comment 7•14 years ago
|
||
For people who can reproduce this... does disabling methodjit make the problem go away? What about disabling tracejit?
Comment 8•14 years ago
|
||
(In reply to comment #7) > For people who can reproduce this... does disabling methodjit make the problem > go away? What about disabling tracejit? Setting javascript.options.methodjit.content to false makes Fx4.0b7 hang on each page of the esep.ch website. Leaving it to true only makes the link mentioned in comment 4 hang Fx. Setting javascript.options.tracejit.content to false fixes the hang.
Comment 9•14 years ago
|
||
This smells a lot like bug 607856, which wasn't fixed in time for beta 7.
Comment 10•14 years ago
|
||
(In reply to comment #9) > This smells a lot like bug 607856, which wasn't fixed in time for beta 7. Dominique, Frédéric, can you try again with a more recent nightly build of Firefox? See http://nightly.mozilla.org/.
Comment 11•14 years ago
|
||
Hum, yes, I cannot reproduce the hang with Mozilla/5.0 (X11; Linux i686; rv:2.0b8pre) Gecko/20101124 Firefox/4.0b8pre
Comment 12•14 years ago
|
||
Thanks, Frédéric. Please reopen if this comes back.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Updated•14 years ago
|
blocking2.0: ? → betaN+
Comment 13•14 years ago
|
||
Sayre you just marked this as a blocker, but it's a dup of another blocker that's been fixed. So I've removed the flag.
blocking2.0: betaN+ → ---
Comment 14•14 years ago
|
||
oh, that's intentional. if this bug were to be reopened, it would be a blocker. but mostly these bugs are like trees falling in the forest with no one around. :)
blocking2.0: --- → betaN+
Comment 15•14 years ago
|
||
(In reply to comment #14) > oh, that's intentional. if this bug were to be reopened, it would be a blocker. Oh. Why would a dup be reopened?
Comment 16•14 years ago
|
||
Bugs can be duped incorrectly (e.g. root cause was assumed to be the same as the other bug, but is actually a different issue).
You need to log in
before you can comment on or make changes to this bug.
Description
•