Closed
Bug 264438
Opened 20 years ago
Closed 18 years ago
100% cpu with javascript on
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: markybob, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041003 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041003 Firefox/0.10.1
visit http://www.msnbc.msn.com/id/6249895/ and wait for page to load. after
the page is loaded (it *is* properly rendered), the cpu shoots up to 100%. i'm
on an AMD64 3500+ with 1GB RAM with nothing running in the backgroup. 'top'
shows that firefox is the culprit.
Reproducible: Always
Steps to Reproduce:
1. visit site
2. wait it to load
3. be forced to close firefox or switch sites to reduce cpu utilization of 100%
Actual Results:
be forced to close firefox or switch sites to reduce cpu utilization of 100%
Expected Results:
not suck up every system resource after page is loaded.
bug duplicated on Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3)
Gecko/20040913 Firefox/0.10.1
Comment 1•20 years ago
|
||
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041017
Firefox/0.9.1+
I am seeing the same thing.
Site uses Shockwave.
I got these messages:
JavaScript error: chrome://browser/content/browser.js, line 478: isBidiEnabled
is not defined
JavaScript error: http://www.msnbc.msn.com/id/6249895/, line 2: logoImg is not
defined
WARNING: PresShell::EndLoad(nsIDocument *) RootScrollFrame is not scrollable?,
file ../../../../../src/layout/html/base/src/nsPresShell.cpp, line 3541
WARNING: nsIFrame::FinishAndStoreOverflow(nsRect*, nsSize) Computed overflow
area must contain frame bounds, file
../../../../../src/layout/html/base/src/nsFrame.cpp, line 4241
![]() |
||
Comment 2•20 years ago
|
||
Is this an issue if Flash is disabled? That is, is it Firefox sucking up CPU,
or the Flash plugin?
Reporter | ||
Comment 3•20 years ago
|
||
this happens to me even without the flash plugin installed. it is firefox
that's the problem
Reporter | ||
Comment 4•20 years ago
|
||
note that even though i can duplicate this on mac osx and linux (with and
without flash), i *cant* duplicate it in windows.
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 5•20 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; fi-FI; rv:1.7.5) Gecko/20041108 Firefox/1.0
Duplicated this bug, clicked the link and I got 100% usage. Windows XP Finnish.
The bug disappeared when I disabled JavaScript, so it is in JavaScript as partly
guessed in the first comment.
Assignee: general → firefox
Product: Mozilla Application Suite → Firefox
QA Contact: general → general
Version: Trunk → 1.0 Branch
Comment 6•20 years ago
|
||
Confirming on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2)
Gecko/20050414 Firefox/1.0+
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•20 years ago
|
OS: Linux → All
Version: 1.0 Branch → unspecified
Comment 7•20 years ago
|
||
This happens regularly for me both on Windows 2000 (Firefox 1.0.2) and on Mac OS
X (Firefox 1.0?). Neither have Flash installed or Java enabled. RAM is not an
issue (1.5 GB on the Mac). It freezes for about 20-30 seconds. On the Mac it
then comes alive for 1-2 secs, then freezes again for another 30 secs (on the PC
it is constantly frozen while the page fault count is galloping upwards). It
even happens when the computer has been idle for several minutes!
It's not being reproduced on my system
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
The page loads a little slowly, but that's probably because it's so full of
junk. There's no hanging or anything like that. I have flash installed and
javascript enabled.
Updated•18 years ago
|
Assignee: bross2 → general
Component: General → JavaScript Engine
Product: Firefox → Core
QA Contact: general → general
Summary: 100% cpu is utilized by firefox and not ever released when visiting site → 100% cpu with javascript on
Version: unspecified → 1.7 Branch
Comment 9•18 years ago
|
||
1.7.x is end of life and the original reporter's page is 404. if you can still reproduce this with a recent 1.8 or 1.9 build please file a new bug. -> WFM.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•