GNOME Bugzilla – Bug 793566
Crash in geary_imap_engine_account_synchronizer_revoke_all
Last modified: 2018-04-13 13:32:41 UTC
Crash in geary_imap_engine_account_synchronizer_revoke_all: Truncated backtrace: Thread no. 1 (10 frames) #0 gee_priority_queue_type1_node_remove at priorityqueue.c:3319 #1 _gee_priority_queue_remove_type1_node at priorityqueue.c:2529 #2 _gee_priority_queue_re_insert at priorityqueue.c:1900 #3 _gee_priority_queue_decrease_key at priorityqueue.c:2051 #4 _gee_priority_queue_delete at priorityqueue.c:1992 #5 gee_priority_queue_iterator_real_remove at priorityqueue.c:3743 #6 gee_priority_queue_real_remove at priorityqueue.c:1186 #7 geary_imap_engine_account_synchronizer_revoke_all at /usr/src/debug/geary-0.12.0-1.fc27.x86_64/src/engine/imap-engine/imap-engine-account-synchronizer.vala:174 #8 geary_imap_engine_account_synchronizer_on_folders_available_unavailable at /usr/src/debug/geary-0.12.0-1.fc27.x86_64/src/engine/imap-engine/imap-engine-account-synchronizer.vala:107 #9 _geary_imap_engine_account_synchronizer_on_folders_available_unavailable_geary_account_folders_available_unavailable at /usr/src/debug/geary-0.12.0-1.fc27.x86_64/src/engine/imap-engine/imap-engine-account-synchronizer.vala:40 There is a better backtrace in https://bugzilla.redhat.com/show_bug.cgi?id=1546551.
https://bugzilla.redhat.com/show_bug.cgi?id=1149919 was reported in 2014, so this has been around for a while.
Original bug report says: "geary crashed when I removed an account while it was indexing it" But I definitely did not remove any accounts when I hit this today.
I just discovered this in Fedora bz last week, seems to be a genuine crash in libgee: Bug 793438 A workaround for this would be a somewhat intrusive change in the engine code, and an equivalent is already on master, but I'll look into it for 0.12.
*** Bug 746506 has been marked as a duplicate of this bug. ***
*** Bug 713967 has been marked as a duplicate of this bug. ***
This is petty annoying, but it is crash-on-exit in one scenario, being low impact, and otherwise an uncommon crash when removing accounts, or when bulk mailbox removal is occurring. So aside from stack traces in disto infrastructure it's not a huge problem. Since the problematic code has already gone away on master, and it seems like it will be a lot of trouble to backport the same work to geary-0.12, I'm going to call this fixed for 0.13.