Version-Release number of selected component: webkitgtk4-2.12.3-1.fc24 Additional info: reporter: libreport-2.7.1 backtrace_rating: 3 cmdline: /usr/libexec/webkit2gtk-4.0/WebKitPluginProcess 77 /usr/lib64/mozilla/plugins/libevbrowserplugin.so crash_function: gdk_window_has_impl executable: /usr/libexec/webkit2gtk-4.0/WebKitPluginProcess global_pid: 3212 kernel: 4.5.5-300.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gdk_window_has_impl at gdkwindow.c:626 #1 _gdk_window_has_impl at gdkwindow.c:627 #2 gdk_x11_window_get_xid at gdkwindow-x11.c:5542 #3 WebKit::NetscapePluginX11::visibilityDidChange at /usr/src/debug/webkitgtk-2.12.3/Source/WebKit2/WebProcess/Plugins/Netscape/x11/NetscapePluginX11.cpp:267 #4 WebKit::PluginControllerProxy::visibilityDidChange at /usr/src/debug/webkitgtk-2.12.3/Source/WebKit2/PluginProcess/PluginControllerProxy.cpp:437 #5 IPC::callMemberFunctionImpl<WebKit::PluginControllerProxy, void (WebKit::PluginControllerProxy::*)(bool), std::tuple<bool>, 0ul>(WebKit::PluginControllerProxy*, void (WebKit::PluginControllerProxy::*)(bool), std::tuple<bool>&&, std::index_sequence<0ul>) at /usr/src/debug/webkitgtk-2.12.3/Source/WebKit2/Platform/IPC/HandleMessage.h:16 #6 IPC::callMemberFunction<WebKit::PluginControllerProxy, void (WebKit::PluginControllerProxy::*)(bool), std::tuple<bool>, std::make_index_sequence<1ul> >(std::tuple<bool>&&, WebKit::PluginControllerProxy*, void (WebKit::PluginControllerProxy::*)(bool)) at /usr/src/debug/webkitgtk-2.12.3/Source/WebKit2/Platform/IPC/HandleMessage.h:22 #7 IPC::handleMessage<Messages::PluginControllerProxy::MutedStateChanged, WebKit::PluginControllerProxy, void (WebKit::PluginControllerProxy::*)(bool)> at /usr/src/debug/webkitgtk-2.12.3/Source/WebKit2/Platform/IPC/HandleMessage.h:92 #8 WebKit::PluginControllerProxy::didReceivePluginControllerProxyMessage at /usr/src/debug/webkitgtk-2.12.3/x86_64-redhat-linux-gnu/DerivedSources/WebKit2/PluginControllerProxyMessageReceiver.cpp:53 #9 WebKit::WebProcessConnection::didReceiveMessage at /usr/src/debug/webkitgtk-2.12.3/Source/WebKit2/PluginProcess/WebProcessConnection.cpp:141 Potential duplicate: bug 1177187
Created attachment 1166115 [details] File: backtrace
Created attachment 1166116 [details] File: cgroup
Created attachment 1166117 [details] File: core_backtrace
Created attachment 1166118 [details] File: dso_list
Created attachment 1166119 [details] File: environ
Created attachment 1166120 [details] File: exploitable
Created attachment 1166121 [details] File: limits
Created attachment 1166122 [details] File: maps
Created attachment 1166123 [details] File: mountinfo
Created attachment 1166124 [details] File: namespaces
Created attachment 1166125 [details] File: open_fds
Created attachment 1166126 [details] File: proc_pid_status
Created attachment 1166127 [details] File: var_log_messages
*** Bug 1177187 has been marked as a duplicate of this bug. ***
*** Bug 1358867 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.
There aren't even any evince frames on the stack...
Honestly it doesn't matter whether it gets reported to WebKit or to Evince, since it's going to the same upstream developer either way, we just have to get it to one place or the other. I still think Evince is a more likely culprit since I've never seen this crash from any other plugin and plugin process crashes almost always turn out to be plugin bugs, but we can use WebKit instead, no matter.
*** Bug 1334971 has been marked as a duplicate of this bug. ***
(In reply to David Tardon from comment #17) > There aren't even any evince frames on the stack... Turns out you were right, it was a WebKit bug!