Description of problem: I'm not sure what exactly made it crash, I saw evolution hanging and then I executed just 'pkill evolution' without -SIGSEGV, after that abrt said it received sigsegv. Version-Release number of selected component: evolution-3.10.4-2.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: evolution crash_function: WTFCrash executable: /usr/bin/evolution kernel: 3.14.8-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 WTFCrash at /lib64/libjavascriptcoregtk-3.0.so.0 #1 WTF::fastMalloc(unsigned long) at /lib64/libjavascriptcoregtk-3.0.so.0 #2 WTF::StringImpl::create(unsigned char const*, unsigned int) at /lib64/libjavascriptcoregtk-3.0.so.0 #3 WTF::String::fromUTF8(unsigned char const*, unsigned long) at /lib64/libjavascriptcoregtk-3.0.so.0 #4 WTF::String::fromUTF8(unsigned char const*) at /lib64/libjavascriptcoregtk-3.0.so.0 #5 WebCore::PluginPackage::fetchInfo() at /lib64/libwebkitgtk-3.0.so.0 #6 WebCore::PluginPackage::createPackage(WTF::String const&, long const&) at /lib64/libwebkitgtk-3.0.so.0 #7 WebCore::PluginDatabase::refresh() at /lib64/libwebkitgtk-3.0.so.0 #8 WebCore::PluginDatabase::installedPlugins(bool) at /lib64/libwebkitgtk-3.0.so.0 #9 PlatformStrategiesGtk::refreshPlugins() at /lib64/libwebkitgtk-3.0.so.0
Created attachment 912497 [details] File: backtrace
Created attachment 912498 [details] File: cgroup
Created attachment 912499 [details] File: core_backtrace
Created attachment 912500 [details] File: dso_list
Created attachment 912501 [details] File: environ
Created attachment 912502 [details] File: exploitable
Created attachment 912503 [details] File: limits
Created attachment 912504 [details] File: maps
Created attachment 912505 [details] File: open_fds
Created attachment 912506 [details] File: proc_pid_status
Created attachment 912507 [details] File: var_log_messages
Thanks for a bug report. I guess you installed some 3rd-party browser plugin which webkigtk3 fails to load. it can be similar to bug #1083306, please read its end for more details on the issue. *** This bug has been marked as a duplicate of bug 1083306 ***