Description of problem: the browser Epiphany, occasionally hangs, not because suddenly occurs in specific system notifications: webkitgtk3 hung Process /usr/libexec/WebKitWebProcess was killed by signal 11 (SIGSEGV) Name: webkitgtk3 Version: libwebkit2gtk-2.0.3-2.fc19 Detected: 28/07/19 PD: I'm using Fedora 19 Version-Release number of selected component: libwebkit2gtk-2.0.3-2.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 3 cmdline: /usr/libexec/WebKitWebProcess 14 crash_function: JSC::DFG::AssemblyHelpers::decodedCodeMapFor(JSC::CodeBlock*) executable: /usr/libexec/WebKitWebProcess kernel: 3.9.9-302.fc19.i686.PAE runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 JSC::DFG::AssemblyHelpers::decodedCodeMapFor(JSC::CodeBlock*) at /lib/libjavascriptcoregtk-3.0.so.0 #1 JSC::DFG::OSRExitCompiler::compileExit(JSC::DFG::OSRExit const&, JSC::Operands<JSC::ValueRecovery, JSC::OperandValueTraits<JSC::ValueRecovery> > const&, JSC::DFG::SpeculationRecovery*) at /lib/libjavascriptcoregtk-3.0.so.0 #2 compileOSRExit at /lib/libjavascriptcoregtk-3.0.so.0 #3 ?? #4 JSC::Interpreter::executeCall(JSC::ExecState*, JSC::JSObject*, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) at /lib/libjavascriptcoregtk-3.0.so.0 #5 JSC::call(JSC::ExecState*, JSC::JSValue, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) at /lib/libjavascriptcoregtk-3.0.so.0 #6 JSC::boundFunctionCall(JSC::ExecState*) at /lib/libjavascriptcoregtk-3.0.so.0 #7 ?? #8 JSC::Interpreter::executeCall(JSC::ExecState*, JSC::JSObject*, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) at /lib/libjavascriptcoregtk-3.0.so.0 #9 JSC::call(JSC::ExecState*, JSC::JSValue, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) at /lib/libjavascriptcoregtk-3.0.so.0
Created attachment 779569 [details] File: backtrace
Created attachment 779570 [details] File: cgroup
Created attachment 779571 [details] File: core_backtrace
Created attachment 779572 [details] File: dso_list
Created attachment 779573 [details] File: environ
Created attachment 779574 [details] File: limits
Created attachment 779575 [details] File: maps
Created attachment 779576 [details] File: open_fds
Created attachment 779577 [details] File: proc_pid_status
Created attachment 779578 [details] File: var_log_messages
Created attachment 779579 [details] File: screencast-1.ogv
Created attachment 779580 [details] File: screencast.ogv
This is https://bugs.webkit.org/show_bug.cgi?id=90728 Epiphany (and other webkit users) on F19 (with webkitgtk3-2.0.4) under i686 does crash a lot. Sometimes the crashes are occasional (e.g. use gmail for a while), certain pages always crash it immediately: http://www.oanda.com/lang/es/currency/converter/ The whole of github e.g. https://github.com/sugarlabs/sugar/pull/40 http://tirania.org/blog/archive/2012/Oct-22.html This is a crash in the "standard" javascript engine in webkit. This engine is actually not used in common configurations - instead a faster system is normally used, which is why this bug has sat around without much attention upstream. The faster engine ("LLint") was disabled in Fedora though, because it was incompatible with Geode LX and similar processors still supported by Fedora i686, https://bugs.webkit.org/show_bug.cgi?id=96286 However, there is a new upstream fix for LLint which makes it work on all i686 processors. https://bugs.webkit.org/show_bug.cgi?id=112239 I have backported that fix locally and it makes things work fine again. I will propose it for inclusion in webkitgtk-2.0.5
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.