Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#6 g_hash_table_resize at ghash.c:565
#7 g_hash_table_maybe_resize at ghash.c:594
#8 g_hash_table_remove_internal at ghash.c:1277
#9 remove_binding_qdata at gbinding.c:221
#10 weak_unbind at gbinding.c:246
#11 weak_refs_notify at gobject.c:2470
#13 handle_mail_request at e-mail-request.c:201
#14 run_in_thread at gsimpleasyncresult.c:871
#15 io_job_thread at gioscheduler.c:89
#16 g_task_thread_pool_thread at gtask.c:1242
Created attachment 918130 [details]
Created attachment 918131 [details]
Created attachment 918132 [details]
Created attachment 918133 [details]
Created attachment 918134 [details]
Created attachment 918135 [details]
Created attachment 918136 [details]
Created attachment 918137 [details]
Created attachment 918138 [details]
Created attachment 918139 [details]
Created attachment 918140 [details]
Created attachment 918141 [details]
I think a change from  should help here. Do you want a test package with that patch included, or you'll create one on your own?
(In reply to Milan Crha from comment #14)
> I think a change from  should help here. Do you want a test package with
> that patch included, or you'll create one on your own?
>  https://bugzilla.gnome.org/show_bug.cgi?id=724023
I could try the package but as I don't have an actual reproducer [*], I'll be fine with fix included in 7.1 :)
[*] this crash happened when evo was in background
Then maybe just have it installed and see whether the crash will reoccur during the normal usage? The crash might happen when the preview panel was updating its content, for whatever reason it triggered it.
Milan, please build the package, thank you.
Created attachment 918438 [details]
This is a backported patch. The upstream patch did not apply cleanly, I forgot of it.
evolution-3.8.5-22.el7_0.1.1 contains the patch, it's currently available at:
Did this help? If yes, then we can mark this as a duplicate of bug #1098358, where I added a similar patch to evolution-3.8.5-25.
Yes, I didn't encounter the crash since.
*** This bug has been marked as a duplicate of bug 1098358 ***