Red Hat Bugzilla – Bug 1281919
[abrt] webkitgtk4: WebKit::NPN_InvokeDefault(NPP, NPObject*, NPVariant const*, uint32_t, NPVariant*)(): WebKitPluginProcess killed by SIGSEGV
Last modified: 2015-11-16 10:53:37 EST
Description of problem:
I was browsing extensions.gnome.org/local and tried to update the extension "TopIcons". Then I got the message that webkit crashed. Epiphany kept running but was unusable and had to be killed.
Version-Release number of selected component:
cmdline: /usr/libexec/webkit2gtk-4.0/WebKitPluginProcess 23 /usr/lib64/mozilla/plugins/libgnome-shell-browser-plugin.so
crash_function: WebKit::NPN_InvokeDefault(NPP, NPObject*, NPVariant const*, uint32_t, NPVariant*)
runlevel: N 5
Thread no. 1 (4 frames)
#0 WebKit::NPN_InvokeDefault(NPP, NPObject*, NPVariant const*, uint32_t, NPVariant*) at /usr/src/debug/webkitgtk-2.10.4/Source/WebKit2/WebProcess/Plugins/Netscape/NetscapeBrowserFuncs.cpp:702
#1 on_shell_signal at browser-plugin.c:306
#2 ffi_call_unix64 at ../src/x86/unix64.S:76
#3 ffi_call at ../src/x86/ffi64.c:525
Created attachment 1093816 [details]
Created attachment 1093817 [details]
Created attachment 1093818 [details]
Created attachment 1093819 [details]
Created attachment 1093820 [details]
Created attachment 1093821 [details]
Created attachment 1093822 [details]
Created attachment 1093823 [details]
Created attachment 1093824 [details]
Should be fixed in https://bodhi.fedoraproject.org/updates/FEDORA-2015-2e33c48936
Sorry, this issue is still present after an update to gnome-shell 3.18.2.
With `GDK_BACKEND=x11 epiphany` I get the crasher after the extension is successfully updated/installed. With wayland GDK Backend (default under Gnome+Wayland) the plugin isn't even loaded.
(In reply to Christian Stadelmann from comment #11)
> Sorry, this issue is still present after an update to gnome-shell 3.18.2.
> With `GDK_BACKEND=x11 epiphany` I get the crasher after the extension is
> successfully updated/installed.
Hm, that's unfortunate, thanks for testing....
> With wayland GDK Backend (default under
> Gnome+Wayland) the plugin isn't even loaded.
We currently have no plans to support plugins under Wayland. Most interesting plugins could never run under Wayland anyway.
*** This bug has been marked as a duplicate of bug 1147314 ***