User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050217 MultiZilla/18.104.22.168d Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050217 MultiZilla/22.214.171.124d After running for a while usually one, sometimes more threads get 100% of the CPU usage although the browser might be in the background, not doing anythig. I'm running on a dual Xeon with hyperthreading enabled (4 logical CPUs) so sometimes Mozilla gets 25% (90% of the cases) and sometimes 50% of the total CPU usage. Even when this happens I can work and the application is stable, but in order to free the CPU I need to restart it. Reproducible: Sometimes Steps to Reproduce: Expected Results: Normal CPU usage.
please try without multizilla
I uninstalled MultiZilla yesterday and this morning the mozilla process was getting 25% of the CPU again so Multizilla is not to blame.
Is there a way on Windows to get a thread dump of the Mozilla process so that one can see which thread is getting all of that CPU time?
does the CPU usage continue if you close everything except 1 window, open a new window and then close the 1 window that you left open? Also please try a clean profile (mozilla -profilemanager)
I had already tried that (closing all windows, then opening a new window and then closing the previously opened window) and the CPU usage stays high. I'll try with a new profile later today and see if it helps.
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.