Version-Release number of selected component: evolution-3.8.3-2.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: evolution crash_function: g_malloc executable: /usr/bin/evolution kernel: 3.9.9-302.fc19.x86_64 runlevel: N 5 uid: 21446 Truncated backtrace: Thread no. 1 (6 frames) #3 g_malloc at gmem.c:159 #4 WebCore::ResourceHandleClient::getBuffer at Source/WebCore/platform/network/ResourceHandleClient.h:107 #5 WebCore::sendRequestCallback at Source/WebCore/platform/network/soup/ResourceHandleSoup.cpp:720 #6 g_simple_async_result_complete at gsimpleasyncresult.c:777 #7 complete_in_idle_cb_for_thread at gsimpleasyncresult.c:845 #12 gtk_main at gtkmain.c:1156
Created attachment 779718 [details] File: backtrace
Created attachment 779719 [details] File: core_backtrace
Created attachment 779720 [details] File: limits
Created attachment 779721 [details] File: proc_pid_status
Thanks for a bug report. It seems to me like a memory corruption bug, recognized when an 8192 B memory block allocation was requested. By any chance, do you know the steps which lead to the crash, please? Not that reproducing a memory corruption is easy, because it depends on the steps before it, the same as on the data.
The crash occurred during mailbox synchronization and simultaneous message opening. Unfortunately, I cannot reproduce this bug. Feel free to close it.
Pity. I'm closing this, but feel free to reopen, in case you'll figure out more details on the issue.