Bug 989453

Summary: [abrt] evolution-3.8.3-2.fc19: g_malloc: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jozef Mlich <jmlich>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: hhorak, jmlich, lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:6de1cb52091be4c677fd5e013807dc179ac0b891
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-31 04:44:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: limits
none
File: proc_pid_status none

Description Jozef Mlich 2013-07-29 09:53:15 UTC 
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
Comment 1 Jozef Mlich 2013-07-29 09:53:24 UTC 
Created attachment 779718 [details]
File: backtrace
Comment 2 Jozef Mlich 2013-07-29 09:53:28 UTC 
Created attachment 779719 [details]
File: core_backtrace
Comment 3 Jozef Mlich 2013-07-29 09:53:31 UTC 
Created attachment 779720 [details]
File: limits
Comment 4 Jozef Mlich 2013-07-29 09:53:34 UTC 
Created attachment 779721 [details]
File: proc_pid_status
Comment 5 Milan Crha 2013-07-30 05:00:05 UTC 
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.
Comment 6 Jozef Mlich 2013-07-30 13:23:53 UTC 
The crash occurred during mailbox synchronization and simultaneous message opening. Unfortunately, I cannot reproduce this bug. Feel free to close it.
Comment 7 Milan Crha 2013-07-31 04:44:37 UTC 
Pity. I'm closing this, but feel free to reopen, in case you'll figure out more details on the issue.