User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 After several hours of work the CPU load (used by Mozilla ~= total) reaches a high level (e.g. 50% or 100%). The task manager shows a constant line, not a peak. The responsiveness of mozilla GUI however is relatively good. Other applications seem to slow down only a little (sometimes noticably - but that may be inteferenced by the virus scanner or sth.). Total CPU measurements: Measurement 1: ~1% at start, after ca. 110 min. -> 50%, after ca 35 Min -> 90%. Measurement 2: ~1% at start, after pretty much exactly 30 min. -> 50%, after pretty much exactly 60 Min -> 100%. No apparent reason. Happens without direct user interaction. Reproducible: Always Steps to Reproduce: 1.Start mail only (not browser), enter passwords to download messages. 2.Work with other applications, read new messages as they arrive. CPU: Pentium 4 (2.6 GHz) with Hyperthreading. (with 50%, the virtual processors show uneven curves approx. 15%  and 85% ) Mozilla profile from previous versions was kept (installed each time the new over old Mozilla). There are several POP (various periods between checking for new mail) and one IMAP account as well as NGs. (Problem happened even if not opening news and browser.) P.S. Don't know which Mozilla component actually responsible.
I have downgraded to Moz 1.4.1 and the problem persists. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4.1) Gecko/20031008 P.S. RAM/pagefile are large and not the issue. Hyperthreading of P4??? Other applications don't have problems.
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.