Description of problem: It happened when I closed an email message I was reading. Version-Release number of selected component: evolution-3.18.2-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: evolution crash_function: free_message_info_data executable: /usr/bin/evolution global_pid: 12619 kernel: 4.2.6-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 11 (8 frames) #0 free_message_info_data at message-list.c:5378 #1 g_hash_table_foreach at ghash.c:1607 #2 ml_sort_uids_by_tree at message-list.c:5493 #3 message_list_regen_thread at message-list.c:5680 #4 run_in_thread at gsimpleasyncresult.c:898 #5 io_job_thread at gioscheduler.c:85 #6 g_task_thread_pool_thread at gtask.c:1287 #8 g_thread_proxy at gthread.c:778
Created attachment 1100629 [details] File: backtrace
Created attachment 1100630 [details] File: cgroup
Created attachment 1100631 [details] File: core_backtrace
Created attachment 1100632 [details] File: dso_list
Created attachment 1100633 [details] File: environ
Created attachment 1100634 [details] File: exploitable
Created attachment 1100635 [details] File: limits
Created attachment 1100636 [details] File: maps
Created attachment 1100637 [details] File: mountinfo
Created attachment 1100638 [details] File: namespaces
Created attachment 1100639 [details] File: open_fds
Created attachment 1100640 [details] File: proc_pid_status
Thanks for a bug report. I guess this is related to a bug #1281331. Could you update the evolution-data-server to the proposed one in that bug and report back, whether the crash still occurs, please?
Unfortunately (or fortunately?), I haven't had this happen since so I will have a hard time verifying it. If you think it's related, then go ahead and close it. In the unlikely case of it happening again, I'll reopen it.
Thanks for the update. I'm closing this for now, but as you said, in case of you manage to reproduce the crash, feel free to reopen this or file a new bug report. Thanks in advance.