After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 390740 - Evolution pegs cpu when connected to overloaded imap server
Evolution pegs cpu when connected to overloaded imap server
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
2.30.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-12-29 18:36 UTC by Shaya Potter
Modified: 2013-08-23 18:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30



Description Shaya Potter 2006-12-29 18:36:31 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:
Comment 1 Daniel Holbach 2007-03-01 11:21:17 UTC
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 ---

Thread 1 (process 7032)

  • #0 pthread_mutex_lock
    from /lib/tls/i686/cmov/libpthread.so.0
  • #1 pthread_mutex_lock
    from /lib/tls/i686/cmov/libc.so.6
  • #2 camel_message_info_free
    at camel-folder-summary.c line 2786
  • #3 maildir_summary_sync
    at camel-maildir-summary.c line 808
  • #4 camel_local_summary_sync
    at camel-local-summary.c line 297
  • #5 local_sync
    at camel-local-folder.c line 498
  • #6 camel_folder_sync
    at camel-folder.c line 273
  • #7 emft_copy_folders__copy
    at em-folder-utils.c line 181
  • #8 mail_msg_received
    at mail-mt.c line 582
  • #9 thread_dispatch
    at e-msgport.c line 1005
  • #10 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #11 clone
    from /lib/tls/i686/cmov/libc.so.6

Comment 2 Jörn Dreyer 2007-11-01 09:56:13 UTC
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.
Comment 3 Matthew Barnes 2008-03-11 00:31:49 UTC
Bumping version to a stable release.
Comment 4 Akhil Laddha 2008-07-17 11:53:48 UTC
Do you still see in current stable release 2.22.3 ?
Comment 5 André Klapper 2008-11-16 19:42:44 UTC
NEEDINFO as per last comment
Comment 6 Sebastien Bacher 2009-03-21 10:54:58 UTC
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
Comment 7 Sebastien Bacher 2009-05-12 08:44:41 UTC
there is a new comment from somebody still having the issue using GNOME 2.26
Comment 8 Akhil Laddha 2009-07-30 13:28:57 UTC
updating the version as per comment#7

Milan, can we mark this bug as a dupe of either bug 570329 or bug 571206
Comment 9 Milan Crha 2009-07-30 15:52:59 UTC
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.
Comment 10 Charly CAULET 2010-04-03 13:28:01 UTC
I'm using evolution 2.30.0.1, and I can confirm that bug.
Comment 11 Charly CAULET 2010-04-04 17:54:21 UTC
(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.
Comment 12 Matthew Barnes 2013-08-23 18:12:26 UTC
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.