Bug 574236 – Evolution can't receive IMAP mail after running a while

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 574236 - Evolution can't receive IMAP mail after running a while


Summary:	Evolution can't receive IMAP mail after running a while


Status:	RESOLVED FIXED

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.26.x (obsolete)
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-03-05 10:00 UTC by Jeff Cai
Modified:	2013-09-13 00:59 UTC

See Also:
GNOME target:	---
GNOME version:	2.25/2.26

Description Jeff Cai 2009-03-05 10:00:35 UTC

I recently upgraded to Evolution 2.25.92 on Ubuntu and Solaris. After running for a while ( one hour or so ), Evolution can't receive any IMAP mail any more.

I can still click the menu commands and switch among the folders. But the message list and preview window are not refreshed.

On Solaris, I found there were a lot of zombie threads. Here is the stack trace when this happens:

19326:  evolution
-----------------  lwp# 1 / thread# 1  --------------------
  feef13b7 pollsys  (8b22208, e, 8046f5c, 0)
  fee970b4 poll     (8b22208, e, 8c, fec614f0, 80a3f6c) + 4c
  fec61508 g_poll   (8b22208, e, 8c, fec52f16) + 24
  fec53343 g_main_context_iterate (80a3f68, 1, 1, 8080080) + 43b
  fec539f1 g_main_loop_run (815e670, 815e670, 804706c, fede4656) + 1dd
  fede46a7 bonobo_main (80471cc, 80470b4, feffb7b4, 0, f9f31a30, 0) + 6b
  080652ad main     (1, 80470f8, 8047100) + 411
  0805ba0a _start   (1, 8047234, 0, 804723e, 8047272, 8047297) + 7a
-----------------  lwp# 54 / thread# 54  --------------------
  fec7b708 g_thread_create_proxy(), exit value = 0x00000000
        ** zombie (exited, not detached, not yet joined) **
-----------------  lwp# 28 / thread# 28  --------------------
  fec7b708 g_thread_create_proxy(), exit value = 0x00000000
        ** zombie (exited, not detached, not yet joined) **
-----------------  lwp# 136 / thread# 136  --------------------
  fec7b708 g_thread_create_proxy(), exit value = 0x00000000
        ** zombie (exited, not detached, not yet joined) **
.....

I'll add the screen output with CAMEL_VERBOSE_DEBUG=1 soon.

Comment 1 Matthew Barnes 2009-03-05 15:34:10 UTC

Hmm, betting those zombie threads originated from the same place.  Would be good to track down where.  Possibly a g_thread_create() call that sets the thread as joinable when it shouldn't be.

Comment 2 Marc Deslauriers 2009-03-07 01:06:23 UTC

I'm seeing this behaviour also since updating to Evolution 2.25.92-0ubuntu2 on Ubuntu Jaunty on amd64.

https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/338581/

Comment 3 Marc Deslauriers 2009-03-07 01:07:59 UTC

Additional detail: When the problem occurs, if I right-click on Inbox and select "properties", it says 0 total messages.

Comment 4 Matthew Barnes 2009-03-07 19:43:44 UTC

I think this is a regression caused by bug #573240.  I reverted the patch in Fedora and IMAP is working much better for me now.  Other distros may want to follow suit.

Jeff, can you confirm this?

Comment 5 Jeff Cai 2009-03-09 08:12:03 UTC

Yes. Confirmed. Reverting the patch can solve this issue.