GNOME Bugzilla – Bug 390740
Evolution pegs cpu when connected to overloaded imap server
Last modified: 2013-08-23 18:12:26 UTC
Please describe the problem: Evolution has the tendancy to peg the cpu for extended periods of time when connected to my overloaded imap server, making the system as a whole less responsive and evolution itself stuck on a mailbox PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 5439 spotter 15 0 178m 79m 16m S 98.2 7.9 9:24.55 evolution eventually I guess the connection times out and it tries to reconnect and the load decreases, but this is a continious problem that's making me consider dumping evolution Steps to reproduce: 1. connect to overload imap server which takes too long to respond to commands 2. wait for a bit. Actual results: evolution pegs the cpu Expected results: evolution shouldn't peg the cpu Does this happen every time? "every" is relatively, it happens many times a day. Other information:
https://launchpad.net/ubuntu/+source/evolution/+bug/76796/comments/4 had a backtrace that matched https://launchpad.net/ubuntu/+source/evolution/+bug/88850 Debug backtrace: --- stack trace ---
+ Trace 114877
Thread 1 (process 7032)
I can confirm this behaviour. My imap runs on a vserver which often is under considerable load and Evolution sometimes just grabs 100% of cpu.
Bumping version to a stable release.
Do you still see in current stable release 2.22.3 ?
NEEDINFO as per last comment
the submitter replied on the ubuntu bug "well, been running evolution for about a day now and can't reproduce, but also haven't had any issues with imap server in ages.", that doesn't mean it's fixed though
there is a new comment from somebody still having the issue using GNOME 2.26
updating the version as per comment#7 Milan, can we mark this bug as a dupe of either bug 570329 or bug 571206
I guess no. This one is about IMAP driving CPU up. The first is about crash, the second about maildir. I'm not sure how to reproduce this, how to make imap server busy enough.
I'm using evolution 2.30.0.1, and I can confirm that bug.
(In reply to comment #10) > I'm using evolution 2.30.0.1, and I can confirm that bug. Actually, this issue seems to happen also with overloaded POP3 servers.
Closing as OBSOLETE since this is too old and vague to do anything with at this point, and I've not observed the described behavior in Evolution 3.8.