GNOME Bugzilla – Bug 760319
[EEwsNotification] Abort session on idle, to avoid deadlock
Last modified: 2016-05-30 12:25:13 UTC
Not quite sure how I triggered this; I was using the addressbook autocompletion from GAL... and then it stopped working. Went into the contacts view in Evolution and found that not working either. This is the Fedora 23 3.18.3-1 build. (gdb) t a a bt
+ Trace 235880
Thread 10 (Thread 0x7f239c967700 (LWP 19644))
Thread 8 (Thread 0x7f239bb28700 (LWP 19675))
Thread 1 (Thread 0x7f23d837d840 (LWP 19568))
*** Bug 761711 has been marked as a duplicate of this bug. ***
This looks like ~3 years ago fixed bug #691399. I think the main issue here is that the soup_session_abort() is called from within the ews_notification_soup_got_chunk(), which is inside of the soup call, thus the soup session is waiting for a finish of that same soup call => starving (it's not a direct deadlock on the locks).
I also made a test build of the evolution-ews, here [1], which prints could interesting information. One to look for contains "this could eventually break for" from "ews_notification_soup_got_chunk". If it'll show up on the evolution console, or the address book factory console, then the bug had been triggered. I believe the change is correct, but I'd prefer if you could verify it too. Another approach would be to use SoupSession, instead of SoupSessionSync, but that has side effects. Created commit d223480 in ews master (3.19.91+) [1] http://koji.fedoraproject.org/koji/taskinfo?taskID=13107555
*** Bug 766944 has been marked as a duplicate of this bug. ***
(In reply to Milan Crha from comment #3) > I also made a test build of the evolution-ews, here [1], > > [1] http://koji.fedoraproject.org/koji/taskinfo?taskID=13107555 Yes, I had that installed but unfortunately evolution-ews-3.18.5-2.fc23.x86_64 has since superseded that and so I cannot check for the interesting information. :-(
Okay, in that case here's a newer scratch build for the Fedora 23: http://koji.fedoraproject.org/koji/taskinfo?taskID=14311701