Description of problem: Just sent an e-mail (which was apparently successfully saved to the Sent box). Version-Release number of selected component: evolution-3.12.11-1.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: evolution crash_function: resort_node executable: /usr/bin/evolution kernel: 3.18.9-200.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: [System Logs]:\n-- Logs begin at sam. 2014-03-15 00:26:09 CET, end at mar. 2015-03-17 11:41:51 CET. -- Truncated backtrace: Thread no. 1 (10 frames) #0 resort_node at e-tree-table-adapter.c:200 #2 e_tree_table_adapter_set_sort_info at e-tree-table-adapter.c:1160 #3 e_tree_set_state_object at e-tree.c:1401 #4 gal_view_etable_attach_tree at gal-view-etable.c:255 #5 mail_paned_display_view_cb at e-mail-paned-view.c:257 #6 mail_paned_view_update_view_instance at e-mail-paned-view.c:952 #10 g_signal_emit_by_name at gsignal.c:3405 #15 mail_reader_emit_folder_loaded at e-mail-reader.c:2960 #16 mail_reader_message_list_built_cb at e-mail-reader.c:2970 #17 _g_closure_invoke_va at gclosure.c:831
Created attachment 1002754 [details] File: backtrace
Created attachment 1002755 [details] File: cgroup
Created attachment 1002756 [details] File: core_backtrace
Created attachment 1002757 [details] File: dso_list
Created attachment 1002758 [details] File: environ
Created attachment 1002759 [details] File: exploitable
Created attachment 1002760 [details] File: limits
Created attachment 1002761 [details] File: maps
Created attachment 1002762 [details] File: open_fds
Created attachment 1002763 [details] File: proc_pid_status
Thanks for a bug report. I do not think there is anything truly odd in the code, at least not in this particular part, even a safety check for non-NULL 'node' variable could be added. That would be just a workaround. I'd guess that you face a fallout of bug #1192773.
Sorry, I don't have a reproducer. Maybe the safety would be good until the root cause is identified.
s/safety/safety check/
Right, let's try that way. I made the change [1] for 3.17.1+ and 3.16.1+. I'm closing this for now, even the root cause was not found here. We can watch the console and see whether it'll repeat again at all. [1] https://git.gnome.org/browse/evolution/commit/?id=c878574