Bug 1570341

Summary: [abrt] evolution: Gigacage::<lambda()>::operator()(): evolution-alarm-notify killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Jonathan Briggs <zlynx>
Component: evolutionAssignee: Milan Crha <mcrha>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: alexl, caillon+fedoraproject, lucilanga, mcrha, rhughes, rstrode, sandmann
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ec0d401be6aaf9800d4eb2376b8cc22c90f31d0e
Whiteboard: abrt_hash:0abd6be6589e247bbfa57d755c4ec7e437138ac8;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-23 09:16:31 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: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Jonathan Briggs 2018-04-22 03:13:20 UTC 
Description of problem:
I logged into my user account.

This system is mostly a server accessed via SSH. I sometimes log into a GUI session.

Because it is a server, overcommit is disabled. I believe this is part of the problem since what I've read about "gigacage" it wants 100 GB of virtual RAM.

It should have a fallback plan because it cannot have 100 GB.

Version-Release number of selected component:
evolution-3.26.6-1.fc27

Additional info:
reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/libexec/evolution/evolution-alarm-notify
crash_function: Gigacage::<lambda()>::operator()
executable:     /usr/libexec/evolution/evolution-alarm-notify
journald_cursor: s=25008ffaca9a431fa395d85cac4284fa;i=152e16f;b=2ee100f00efd4b0fa498a46dacc18d0d;m=7fef6a61ae;t=56a6728de2e6b;x=bc5badd1559c20c3
kernel:         4.15.15-300.fc27.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 Gigacage::<lambda()>::operator() at /usr/src/debug/webkitgtk4-2.20.1-1.fc27.x86_64/Source/bmalloc/bmalloc/Gigacage.cpp:155
 #1 std::__invoke_impl<void, Gigacage::ensureGigacage()::<lambda()> > at /usr/include/c++/7/bits/invoke.h:60
 #2 std::__invoke<Gigacage::ensureGigacage()::<lambda()> > at /usr/include/c++/7/bits/invoke.h:95
 #3 std::<lambda()>::operator() at /usr/include/c++/7/mutex:672
 #5 std::<lambda()>::_FUN(void) at /usr/include/c++/7/mutex:677
 #6 __pthread_once_slow at pthread_once.c:116
 #7 __gthread_once at /usr/include/c++/7/x86_64-redhat-linux/bits/gthr-default.h:699
 #8 std::call_once<Gigacage::ensureGigacage()::<lambda()> > at /usr/include/c++/7/mutex:684
 #9 Gigacage::ensureGigacage at /usr/src/debug/webkitgtk4-2.20.1-1.fc27.x86_64/Source/bmalloc/bmalloc/Gigacage.cpp:108
 #10 bmalloc::Heap::Heap at /usr/src/debug/webkitgtk4-2.20.1-1.fc27.x86_64/Source/bmalloc/bmalloc/Heap.cpp:58
Comment 1 Jonathan Briggs 2018-04-22 03:13:26 UTC 
Created attachment 1425203 [details]
File: backtrace
Comment 2 Jonathan Briggs 2018-04-22 03:13:27 UTC 
Created attachment 1425204 [details]
File: cgroup
Comment 3 Jonathan Briggs 2018-04-22 03:13:28 UTC 
Created attachment 1425205 [details]
File: core_backtrace
Comment 4 Jonathan Briggs 2018-04-22 03:13:28 UTC 
Created attachment 1425206 [details]
File: cpuinfo
Comment 5 Jonathan Briggs 2018-04-22 03:13:30 UTC 
Created attachment 1425207 [details]
File: dso_list
Comment 6 Jonathan Briggs 2018-04-22 03:13:31 UTC 
Created attachment 1425208 [details]
File: environ
Comment 7 Jonathan Briggs 2018-04-22 03:13:32 UTC 
Created attachment 1425209 [details]
File: exploitable
Comment 8 Jonathan Briggs 2018-04-22 03:13:33 UTC 
Created attachment 1425210 [details]
File: limits
Comment 9 Jonathan Briggs 2018-04-22 03:13:34 UTC 
Created attachment 1425211 [details]
File: maps
Comment 10 Jonathan Briggs 2018-04-22 03:13:35 UTC 
Created attachment 1425212 [details]
File: mountinfo
Comment 11 Jonathan Briggs 2018-04-22 03:13:36 UTC 
Created attachment 1425213 [details]
File: open_fds
Comment 12 Jonathan Briggs 2018-04-22 03:13:37 UTC 
Created attachment 1425214 [details]
File: proc_pid_status
Comment 13 Milan Crha 2018-04-23 09:16:31 UTC 
Thanks for a bug report. Please see bug #1564970 for further information how to workaround the crash. As you do not use GUI part of the system often, I'd say you can disable evolution-alarm-notify from the auto-start applications too. Without that you won't get notifications about upcoming events (the reminders for those events), which may or may not be a problem for you.

*** This bug has been marked as a duplicate of bug 1564970 ***