Description of problem: Epiphany became unresponsive, and I had to kill it Version-Release number of selected component: epiphany-3.10.2-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: epiphany crash_function: g_type_check_instance_cast executable: /usr/bin/epiphany kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1236200002 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_cast at gtype.c:4008 #1 get_domains_with_cookies_cb at pdm-dialog.c:1003 #2 g_task_return_now at gtask.c:1108 #3 g_task_return at gtask.c:1161 #4 webkitCookieManagerGetDomainsWithCookiesCallback at Source/WebKit2/UIProcess/API/gtk/WebKitCookieManager.cpp:213 #5 performCallbackWithReturnValue at Source/WebKit2/UIProcess/GenericCallback.h:128 #6 WebKit::WebCookieManagerProxy::didGetHostnamesWithCookies at Source/WebKit2/UIProcess/WebCookieManagerProxy.cpp:124 #7 callMemberFunction<WebKit::WebCookieManagerProxy, void (WebKit::WebCookieManagerProxy::*)(WTF::Vector<WTF::String> const&, unsigned long), WTF::Vector<WTF::String>, unsigned long> at Source/WebKit2/Platform/CoreIPC/HandleMessage.h:27 #8 handleMessage<Messages::WebCookieManagerProxy::DidGetHostnamesWithCookies, WebKit::WebCookieManagerProxy, void (WebKit::WebCookieManagerProxy::*)(WTF::Vector<WTF::String> const&, unsigned long)> at Source/WebKit2/Platform/CoreIPC/HandleMessage.h:376 #9 WebKit::WebCookieManagerProxy::didReceiveMessage at DerivedSources/WebKit2/WebCookieManagerProxyMessageReceiver.cpp:41
Created attachment 841919 [details] File: backtrace
Created attachment 841920 [details] File: cgroup
Created attachment 841921 [details] File: core_backtrace
Created attachment 841922 [details] File: dso_list
Created attachment 841923 [details] File: environ
Created attachment 841924 [details] File: exploitable
Created attachment 841925 [details] File: limits
Created attachment 841926 [details] File: maps
Created attachment 841927 [details] File: open_fds
Created attachment 841928 [details] File: proc_pid_status
Created attachment 841929 [details] File: var_log_messages
Created attachment 841930 [details] File: binary
*** Bug 1033838 has been marked as a duplicate of this bug. ***
*** Bug 1048526 has been marked as a duplicate of this bug. ***
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
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.