GNOME Bugzilla – Bug 617261
evolution didn't quit due to deadlock
Last modified: 2010-06-10 17:12:02 UTC
evolution 2.31.1 What i did : evolution were fetching mails via imapx, disabled account in the mean while and clicked on 'X' to quit evolution but it didn't quit. Program received signal SIGINT, Interrupt. 0xffffe430 in __kernel_vsyscall () (gdb) t a a bt
+ Trace 221624
I just got the same with MAPI, the cfs_reload_from_db holds the db lock, but requests SUMMARY_LOCK, where the other thread holds SUMMARY_LOCK, but requests db lock. These two are waiting on each other.
Created attachment 161852 [details] [review] proposed eds patch for evolution-data-server; Thus holding summary lock before db lock should fix the issue. Could you give it a try let me know, please? Thanks in advance.
I had a similar issue on gnome-2-30 too, though it would be safer to commit after patch for bug #550414, though it's still under testing. (The change there good for this bug is to create a recursive locks from mutexes used in camel folder summary, to not get into locking issue.
+ Trace 222194
Created commit ed3eb6b in eds master (2.31.3+)
*** Bug 621221 has been marked as a duplicate of this bug. ***
Created commit ceb691f in eds gnome-2-30 (2.30.2+)