instance of Mozilla in System Manager using 40+% resources



13 years ago
13 years ago


(Reporter: Alan Smedley, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)




13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050205
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050205

I follow the regular Nightly Builds of Mozilla, installing a new copy often
daily.  If I do not completly remove the old files in the \Program Files\Common
Files\\GRE\<Previous Version Directory Name>\ directory tree and give
the computer Registry a clean out with CleanReg and "Ace Utilities" and Cleaning
out the Mozilla Cache before installing I will often get heavy CPU usage on at
least on instance of Mozilla in the System Manager.  This can be up to 40+%. 
Killing that instance off without also cleaning up will not permanantly fix the

Reproducible: Sometimes

Steps to Reproduce:
1.Install various Nightly builds one after the other without cleaning out
2.Watch the System Manager for multiple instances of Mozilla

Actual Results:  
Not on all Nightly builds but on many (2 out of 3) it will start to affect CPU
performance which will be degraded.

Expected Results:  
On installing each new version a better cleanup of all the entries in the system
registry and of the old files should be performed as the OS seems to also find
and use files from each <nightly> driectory.  Also the Cache should be cleared
better at install time
Summary: instance of Mozilla in System Manager useing 40+% resources → instance of Mozilla in System Manager using 40+% resources
Version: unspecified → Trunk
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.