Closed
Bug 231600
Opened 22 years ago
Closed 22 years ago
Tight JavaScript loop causes 100% CPU usage
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: erice, Unassigned)
References
()
Details
(Keywords: qawanted)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
Whenever I click on a link from the man ESPN page my browser hangs and I have to
use "task Manager" to kill it. I think this is in the JavaScript code that
would create the pop-up advertizing if I didn't have it blocked.
I think that this might be intentional on the part of ESPN to keep people who
block the pop-ups from viewing the page.
Reproducible: Always
Steps to Reproduce:
1. Go to espn.go.com
2. Click on anything
3.
Actual Results:
Mozilla becomes EXTREMELY sluggish (30 sec. to respond to an attempt to scroll
the window). "Task Manager" shows 100% CPU usage.
Expected Results:
Kill the execution of this JavaScript code.
Comment 1•22 years ago
|
||
I'm unable to reproduce this. Reporter, do you have any extensions or unusual
options installed? I have popup-blocking on and see barely any js activity when
loading that page. Is there a reduced testcase that shows this problem (js loop
that doesn't bring up the kill scripts dialog)?
If the dialog just takes a long time to appear, then dupe this to bug 13350.
Assignee: general → general
Component: JavaScript Engine → DOM
Keywords: qawanted
QA Contact: PhilSchwartau → ian
Comment 2•22 years ago
|
||
Reporter could you please try to whitelist espn.com in the popup manager list
and see what happens? If that doesn't work could you please try to use a build
which has the fix for bug 13350? (that is all builds after feb 13).
Thanks in advance!
| Reporter | ||
Comment 3•22 years ago
|
||
Sorry about this. It turns out the problem was with using the QuickTime Plugin
to handle the Flash content. The in page flash animation is only shown if
javascript is enabled.
This is not a bug with Mozilla.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
Updated•7 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•