286088 - After client upgrade to latest Firefox version (1.01), browser hogs system resources repeatedly for overall slow PC performance

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Philip Hunt]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1

Every few seconds after starting and using the browser to go to a variety of 
Web sites, the system resources used on the PC peak to 100% and affect not 
only use of the browser, but use of other applications while system resources 
are being hogged by Firefox.

Reproducible: Always

Steps to Reproduce:
1.  Start Firefox client software (v. 1.01)
2.  Try to browse any number of Web sites 
3.  Every few seconds, usage of system resources peaks at 100% and slows 
EVERYTHING down.

Actual Results:  
Every resource on my PC slows down since Firefox is hogging all available 
system resources every few seconds.

Expected Results:  
It should NOT be a consistent resource hog, and allow quick and easy access 
from within the browser, as well as from other applications running on the PC.

The PC system on which the bug is occuring is a Dell Dimension 8400 with a 
3.40GHz processor, 4.0 GB of memory and an ATI Radeon X800 XT video card.

Comment 1

[cablesurfr]

After upgrade the performance is horrible.  Mozilla/5.0 (Windows; U; Windows NT
5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1

Comment 2

[Frank de Lange]

Same here, FF (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050317
Firefox/1.0.2) regularly hogs the CPU for a minute or so without any obvious
cause or reason. Waiting out the hogs usually brings the browser back to life.

Yes, there's a few extensions on this system: Adblock, Flashblock, Web Developer
and Mozimage.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.