Version-Release number of selected component: epiphany-3.10.0-1.fc20 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: epiphany crash_function: equal executable: /usr/bin/epiphany kernel: 3.11.2-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 equal at Source/WTF/wtf/text/StringImpl.h:1127 #2 equalInner at Source/WTF/wtf/text/StringImpl.cpp:1259 #3 WTF::StringImpl::endsWith at Source/WTF/wtf/text/StringImpl.cpp:1318 #4 endsWith<2u> at Source/WTF/wtf/text/StringImpl.h:772 #6 WebCore::pathByAppendingComponent at Source/WebCore/platform/gtk/FileSystemGtk.cpp:165 #7 WebKit::findWebKitProcess at Source/WebKit2/Shared/gtk/ProcessExecutablePathGtk.cpp:61 #8 WebKit::executablePathOfWebProcess at Source/WebKit2/Shared/gtk/ProcessExecutablePathGtk.cpp:71 #9 WebKit::ProcessLauncher::launchProcess at Source/WebKit2/UIProcess/Launcher/gtk/ProcessLauncherGtk.cpp:80 #10 operator() at Source/WTF/wtf/Functional.h:704 #11 performWork at Source/WebKit2/Platform/gtk/WorkQueueGtk.cpp:49
Created attachment 807415 [details] File: backtrace
Created attachment 807416 [details] File: cgroup
Created attachment 807417 [details] File: core_backtrace
Created attachment 807418 [details] File: dso_list
Created attachment 807419 [details] File: environ
Created attachment 807420 [details] File: exploitable
Created attachment 807421 [details] File: limits
Created attachment 807422 [details] File: maps
Created attachment 807423 [details] File: open_fds
Created attachment 807424 [details] File: proc_pid_status
Created attachment 807425 [details] File: var_log_messages
I run into this bug very often. Seems to happen about every time I close Epiphany. One thing that might be related: Epiphany (the process) takes very long to exit after closing the window.
Another user experienced a similar problem: After browsing a web site that makes heavy use of ".aspx" pages (and causes Firefox to crash almost instantly), I exit Epiphany and then the crash occurs. reporter: libreport-2.1.10 backtrace_rating: 3 cmdline: epiphany crash_function: equal executable: /usr/bin/epiphany kernel: 3.12.6-300.fc20.x86_64 package: epiphany-3.10.3-1.fc20 reason: epiphany killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Just exited a normal browsing session. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: epiphany crash_function: equal executable: /usr/bin/epiphany kernel: 3.14.8-200.fc20.x86_64 package: epiphany-3.10.3-1.fc20 reason: epiphany killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.