Bug 1023826

Summary: [abrt] evolution-3.8.5-2.fc19: WTF::OSAllocator::reserveUncommitted(unsigned long, WTF::OSAllocator::Usage, bool, bool, bool): Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Brian J. Murrell <brian>
Component: webkitgtk3Assignee: Matthias Clasen <mclasen>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: fedora, kalevlember, lucilanga, mbarnes, mclasen, mcrha, tpopela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:03eea43df8d55f57bb330875cfbc9ebbd9d89011
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-13 11:45:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Brian J. Murrell 2013-10-28 02:56:48 UTC 
Description of problem:
Trying to start evolution.

There is definitely old data lying around as I have not used evolution on this machine in probably years now.  I want to give it a go again.

Version-Release number of selected component:
evolution-3.8.5-2.fc19

Additional info:
reporter:       libreport-2.1.8
backtrace_rating: 4
cmdline:        evolution
crash_function: WTF::OSAllocator::reserveUncommitted(unsigned long, WTF::OSAllocator::Usage, bool, bool, bool)
executable:     /usr/bin/evolution
kernel:         3.11.4-201.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1001

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 WTF::OSAllocator::reserveUncommitted(unsigned long, WTF::OSAllocator::Usage, bool, bool, bool) at /lib64/libjavascriptcoregtk-3.0.so.0
 #1 JSC::ExecutableAllocator::initializeAllocator() at /lib64/libjavascriptcoregtk-3.0.so.0
 #2 JSC::initializeThreading() at /lib64/libjavascriptcoregtk-3.0.so.0
 #3 webkitInit at /lib64/libwebkitgtk-3.0.so.0
 #4 webkit_web_view_class_intern_init(void*) at /lib64/libwebkitgtk-3.0.so.0
 #5 type_class_init_Wm at gtype.c:2244
 #6 g_type_class_ref at gtype.c:2959
 #9 g_object_new_valist at gobject.c:1797
 #11 mail_paned_view_constructed at e-mail-paned-view.c:639
 #13 g_object_new_valist at gobject.c:1836
Comment 1 Brian J. Murrell 2013-10-28 02:56:52 UTC 
Created attachment 816673 [details]
File: backtrace
Comment 2 Brian J. Murrell 2013-10-28 02:56:54 UTC 
Created attachment 816674 [details]
File: cgroup
Comment 3 Brian J. Murrell 2013-10-28 02:56:57 UTC 
Created attachment 816675 [details]
File: core_backtrace
Comment 4 Brian J. Murrell 2013-10-28 02:57:00 UTC 
Created attachment 816676 [details]
File: dso_list
Comment 5 Brian J. Murrell 2013-10-28 02:57:03 UTC 
Created attachment 816677 [details]
File: environ
Comment 6 Brian J. Murrell 2013-10-28 02:57:06 UTC 
Created attachment 816678 [details]
File: exploitable
Comment 7 Brian J. Murrell 2013-10-28 02:57:08 UTC 
Created attachment 816679 [details]
File: limits
Comment 8 Brian J. Murrell 2013-10-28 02:57:11 UTC 
Created attachment 816680 [details]
File: maps
Comment 9 Brian J. Murrell 2013-10-28 02:57:13 UTC 
Created attachment 816681 [details]
File: open_fds
Comment 10 Brian J. Murrell 2013-10-28 02:57:16 UTC 
Created attachment 816682 [details]
File: proc_pid_status
Comment 11 Brian J. Murrell 2013-10-28 02:57:19 UTC 
Created attachment 816683 [details]
File: var_log_messages
Comment 12 Milan Crha 2013-11-05 17:10:40 UTC 
Thanks for a bug report. I move this to webkigtk3, because the crash happens there, even the backtrace shows that the crash happened when a webkit's web view object instance was about to initialize, which is quite odd place to get a crash in. Maybe as a starter, could you try to update webkitgtk3 to the latest version, please?

(the val_log_messages shows:
   evolution[4694]: segfault at bbadbeef ip 000000391ba8365f sp 00007fff6fc526b0 error 6 in libjavascriptcoregtk-3.0.so.0.13.16[391b600000+559000])
Comment 13 Brian J. Murrell 2013-11-12 12:53:38 UTC 
I think ultimately this happened because I had my VM ulimit set to 2GB.  It seems pretty crazy that tools that use webkit need more than 2GB of VM.

In any case, removing the ulimit seems to have rectified this.
Comment 14 Milan Crha 2013-11-13 11:45:35 UTC 
Ah, I see. I would not expect it being it. Let me close this, because if it's about memory limits, then the crash sort-of makes sense. Not that I agree with high memory usage of evolution, it's just the opposite.