Bug 733523 - Repeatable evolution hang
Summary: Repeatable evolution hang
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 15
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-25 21:51 UTC by Jerry James
Modified: 2011-08-26 13:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-26 06:43:53 UTC


Attachments (Terms of Use)
Backtrace of evolution process (9.32 KB, text/x-log)
2011-08-25 21:51 UTC, Jerry James
no flags Details
Backtrace of evolution-alarm-notify process (1.82 KB, text/x-log)
2011-08-25 21:52 UTC, Jerry James
no flags Details


Links
System ID Priority Status Summary Last Updated
GNOME Bugzilla 657404 None None None Never

Description Jerry James 2011-08-25 21:51:54 UTC
Created attachment 519985 [details]
Backtrace of evolution process

Description of problem:
I recently added a second account to my Evolution setup, both with IMAP servers (not IMAP+, just vanilla IMAP).  Since then, Evolution has hung every single day; I don't know if there is a causal relationship.  It usually runs for several hours before hanging; I typically notice the hang an hour or two before quitting time.

I'll attach a backtrace of both the stuck Evolution process, and the only other evolution-related process I see running, which is evolution-alarm-notify.

Version-Release number of selected component (if applicable):
evolution-3.0.2-3.fc15.x86_64

How reproducible:
About once per day.

Steps to Reproduce:
1. Start evolution first thing in the morning.
2. Wait.
3.
  
Actual results:
Evolution eventually hangs.

Expected results:
Evolution should never hang.

Additional info:
Sometimes it is doing nothing when the hang occurs.  The backtrace I'm attaching, though, is for an Evolution that shows one "Scanning folders in IMAP server foo' and one "Pinging IMAP server foo" message on the bottom.  Should it be scanning folders in an IMAP server that it is also pinging?

Comment 1 Jerry James 2011-08-25 21:52:35 UTC
Created attachment 519986 [details]
Backtrace of evolution-alarm-notify process

Comment 2 Milan Crha 2011-08-26 06:43:53 UTC
Thanks for a bug report. I do not see any thread doing anything special from evolution, the only thing is a waiting for a lock in thread 1, which locks UI:
Thread 1 (Thread 0x7f7b50f409a0 (LWP 20000)):
#0  __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:140
#1  0x00000030b8409ad6 in _L_lock_752 () from /lib64/libpthread.so.0
#2  0x00000030b84099d7 in __pthread_mutex_lock (mutex=0xa891b8) at pthread_mutex_lock.c:65
#3  0x00000030b983f835 in g_source_attach (source=0x322b27e0, context=0xa891b0) at gmain.c:963
#4  0x00000030b9844d25 in g_idle_add_full (priority=200, function=0x3266689660 <mail_msg_free>, data=0x23c838a0, notify=0) at gmain.c:4620
#5  0x0000003266689bf9 in mail_msg_idle_cb () at mail-mt.c:390
#6  0x00000030b98427ed in g_main_dispatch (context=0xa891b0) at gmain.c:2441
#7  g_main_context_dispatch (context=0xa891b0) at gmain.c:3014
#8  0x00000030b9842fc8 in g_main_context_iterate (context=0xa891b0, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3092
#9  0x00000030b984360d in g_main_loop_run (loop=0x100e9f0) at gmain.c:3300
#10 0x0000003d3c14736d in gtk_main () at gtkmain.c:1358
#11 0x00000000004023a0 in main (argc=1, argv=0x7fff8ba63538) at main.c:734

and there are only two things from evolution here, frame #11 in main()
and frame #5, which is just adding some idle callback. Thus this seems to me like something with latest glib on the first look.

Anyway, I moved this upstream as [1]. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=657404

Comment 3 Jerry James 2011-08-26 13:59:17 UTC
I have CCed myself to the upstream bug.  Thanks, Milan.


Note You need to log in before you can comment on or make changes to this bug.