GNOME Bugzilla – Bug 761711
deadlocks when deleting multiple messages in EWS account.
Last modified: 2016-02-23 13:40:13 UTC
Created attachment 320623 [details] t a a bt of deadlocked evolution When I try to delete a number (the exact quantity to trigger is unknown) of messages in an EWS account, I end up with a lot of "Storing changes in folder" threads and typically a "Refreshing folder 'Inbox'" and Evolution pretty much useless at that point as it does not actually refresh the Inbox and needs to be killed and restarted to get it doing something useful again. I will attach a 't a a bt' for the evolution process stuck in this state.
Thanks for a bug report. If I read the backtrace properly, then there happened something to your network connection and the EWS server was not reachable. That made evolution-ews disconnect from the server. Some threads are in this disconnect state, waiting for libsoup to finish session abort, which it turn is waiting for some libsoup internal condition (GCond) to be signalled. Other threads, related to what you see in the status bar, are trying to connect, but that cannot happen before the disconnect phase is over. The libsoup threads are Thread 14 and Thread 16, both doing the same thing on the same soup session object.
Created attachment 321950 [details] t a a bt of deadlocked evolution I've got another situation where Evolution is deadlocked on EWS operations. I have not seen any new mail in my EWS INBOX since over 12 hours and I have a number of threads "Storing changes in folder 'Inbox' as well as a "Moving messages into folder Inbox/foo" It is possible that when this all started I had lost my VPN connection to the LAN where the EWS servers are but it was re-established shortly after losing it. Surely Evolution should be able to restore it's state and resume operations upon reconnection of the VPN, even if it means getting a new IP address, yes?
From IRC, this involves libsoup-2.52.2-1.fc23.x86_64. It's the same thing as bug #760319, thus I mark this as a duplicate of it. *** This bug has been marked as a duplicate of bug 760319 ***