Closed Bug 293570 Opened 20 years ago Closed 19 years ago

excessive CPU usage with unreachable IMAP server

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: sofar, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050418 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050418 Firefox/1.0.3

When accessing remote folders on an unreliable IMAP connection CPU usage goes to
60% (2.6GHz Cpu), spinning idle while waiting for the connection to re-establish.

Reproducible: Always

Steps to Reproduce:
1. write a small message
2. unplug network cable / drop route on router to IMAP server
3. click send, see TB tries to save the message on the IMAP server 'Sent' folder


Actual Results:  
4. notice excessive CPU usage
5. After the attempt to save to the IMAP server fails, CPU faills back to normal
6. click 'retry'
7. notice again excessive CPU usage until IMAP server is reachable

Expected Results:  
During network timeouts, CPU usage should be absolute minimum by the
corresponding thread

* buggy corporate firewall :^)
* also confirmed with flaky wifi
* tb-1.0.2

possibly related bugs:
#286091, #284135, #228201
exemplary output of typical CPU usage (3 second intervals):

$ top b | grep 1365
 1365 auke      18   0 50948  49m  20m S 46.9 10.6  14:29.01 0 thunderbird-bin
 1365 auke      15   0 50948  49m  20m R 50.5 10.6  14:30.54 0 thunderbird-bin
 1365 auke      19   0 50948  49m  20m S 48.8 10.6  14:32.02 0 thunderbird-bin
 1365 auke      19   0 50948  49m  20m S 49.5 10.6  14:33.52 0 thunderbird-bin
 1365 auke      16   0 50948  49m  20m R 52.5 10.6  14:35.11 0 thunderbird-bin
 1365 auke      18   0 50948  49m  20m S 52.1 10.6  14:36.69 0 thunderbird-bin
I use imap only (windows). The last days Thunderbird has almost been useless.
After a few minutes it starts to use 99% CPU.

The only thing I can remember that has changed before this problem started is
that I installed "DU Super Controler". This is a load balance software I use to
limit the upload speed on my computer to 10kb.
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
Closed: 19 years ago
Resolution: --- → EXPIRED
reporter writes "I have not been using Thunderbird in a couple of years now. "
Status: RESOLVED → VERIFIED
(In reply to comment #5)
> reporter writes "I have not been using Thunderbird in a couple of years now. "

really? I do not recall using anything else BUT thunderbird in the last years.

Regarding this bug: it seems to be fixed anyway. a quick test shows CPU utilization is acceptably low when the IMAP connection fails.
Resolution: EXPIRED → FIXED
thanks for updating the bug - WORKSFORME is then the appropriate resolution

odd, I cut and paste people's quotes so a mistake in comment 5 seems unlikely.
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.