Closed
Bug 326031
Opened 19 years ago
Closed 14 years ago
CPU remains around 50%
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: air_run82, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1 There might already be a bug that describes the problem that firefox has with this webpage. For some reason this webpage makes the CPU Usage remain around 50%. I haven't looked at it close enough to figure it out and even if I did I might not be able to find the reason. So I'm leaving it up to you guys to find the exact problem. Reproducible: Always Steps to Reproduce: 1.Just go the website and watch the CPU Usage
The CPU usage drops to 0% when I stop the scrolling text under 'Upcoming Events' (premade script: http://www.softcomplex.com/products/tigra_scroller_pro/) by hovering over it with my mouse cursor, duplicate of/related to Core bug 142994?
Updated•17 years ago
|
Whiteboard: DUPEME
Version: unspecified → 1.5.0.x Branch
Comment 2•14 years ago
|
||
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME http://www.mozilla.com http://support.mozilla.com/kb/Managing+profiles http://support.mozilla.com/kb/Safe+mode
Comment 3•14 years ago
|
||
No reply, INCOMPLETE. Please retest with Firefox 3.6.3 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: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•