© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid) Firefox/3.6.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.3a5pre) Gecko/20100426 Shredder/3.2a1pre
Symptom: any progress bar that appears seems to bring with it a pegged CPU core.
I suggest it's the progress bar code that is polling the CPU. If I send a message, and the send process fails for some reason, the progress bar continues to animate, while a new dialog box appears with a reason for error. Meanwhile, a CPU core is still pegged, even though there is no "real" work being done, just the progress bar animation.
I've noticed the high CPU core usage with *any* progress bar activity, not just the above example. For example, on this latest build, the progress bar in the lower right is attempting to complete while I type this bug report, I presume while it indexes for the first time (first time with /this/ build) my inbox,(>8000 messages). Meanwhile, my CPU graph shows one core in full usage.
Reproducible: Always
Steps to Reproduce:
Here is one method to get a status bar
1. Open Thunderbird.
2. Clear your password
3. Send a message
4. Type in an incorrect password
5. Note the CPU usage when it gives you the SMTP error dialog.
If it matters, I'm using IMAP, but again, I doubt that's the issue. I think it's the scroll bar code.
Actual Results:
When any progress bar is visible, a processor goes berserk.
Expected Results:
When any progress bar is visible, the CPU usage caused by the progress bar should be pert near zero.
These bugs may be relevant, or may turn out to be duplicates. I couldn't quite tell from the descriptions:
https:/
https:/
https:/