Closed Bug 293689 Opened 20 years ago Closed 20 years ago

High CPU usage

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: johnkbird, Unassigned)

References

()

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 Similar to ID 288472 (MAC) - Firefox open a few hours, opened and closed a few tabs, Firefox looks to be idle (not loading any pages) but CPU usage high and stays stable - sometimes 55%, 65%, sometimes 95%. Always Firefox is the offending process. Closing Firefox and reopening the same pages again cures the problem. Has happened since version 1.0.0 - had the problem probably 10- 15 times. No unusual web sites - Yahoo mail, tucows and links from Tucows in the last case. Yahoo mail is often open when this happens - dunno if this is coincidence. Have a nice screen shot showing this with Firefox idle and systinternals and taskmanager both showing the high CPU. WIndows XP SP2 Sony Vaio laptop (Athlon processor). Reproducible: Sometimes Actual Results: Firefox idle, but CPU usuage steady on a high value - eg 55% to 95%. Expected Results: If firefox shows it is not loading a page, CPU usage should be around 0-5% I have screen shots showing this in more detail if you would like.
60 days inactive: INVALID in 72 hours. Is this reproducable with a nightly build (http://www.mozilla.org/developer)?
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Exerpt from email: I was having this problem consistently with Firefox until a couple of weeks ago...current update of 1.0.4 seems OK so far.... Symptom was after a couple of days of Firefox open, and opening and closing lots of tabs (15/20) it would start to eat lots of CPU while doing nothing - ie no pages loading or refreshing. <- WORKSFORME
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.