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
Created attachment 1425203 [details] File: backtrace
Created attachment 1425204 [details] File: cgroup
Created attachment 1425205 [details] File: core_backtrace
Created attachment 1425206 [details] File: cpuinfo
Created attachment 1425207 [details] File: dso_list
Created attachment 1425208 [details] File: environ
Created attachment 1425209 [details] File: exploitable
Created attachment 1425210 [details] File: limits
Created attachment 1425211 [details] File: maps
Created attachment 1425212 [details] File: mountinfo
Created attachment 1425213 [details] File: open_fds
Created attachment 1425214 [details] File: proc_pid_status
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 ***