Closed
Bug 426638
Opened 17 years ago
Closed 15 years ago
High CPU usage
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: lifeispeachy978, Unassigned)
Details
(Whiteboard: [CLOSE 2010-09-15])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5 Creative ZENcast v2.00.13
Build Identifier: Firefox/3.0b5
An hour or so after having installed the latest beta (3b5) Firefox started to increase its CPU usage up until 50% and hovers between there and 45% continuously. It doesn't resolve itself when left for an extended period of time.
Reproducible: Couldn't Reproduce
Steps to Reproduce:
1.Restarted Firefox, it didn't happen again and FF's CPU usage stays at about 17%(still somewhat high IMO)
2.
3.
I'm reasonably sure it will start again, however something must have triggered it and so far I haven't figured out what. If I come across it I'll file another bug report/modify this one if that's possible.
Reproduced it today whilst on YouTube. It started all of a sudden so I think it's probably unrelated to any particular web pages.
Comment 2•17 years ago
|
||
Maybe the sites are using bad javascripts, only meant for internet explorer, so maybe blocking some problematic ads or other objects in pages with an extension like adblock plus is an option for you.
https://addons.mozilla.org/en-US/firefox/search?q=adblock&status=4
Comment 4•15 years ago
|
||
Reporter, are you still seeing this issue with Firefox 3.6.x or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Comment 5•15 years ago
|
||
No reply, INCOMPLETE. Please retest with Firefox 3.6.11 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•