Bug 1147314

Summary: [abrt] webkitgtk4: WebKit::NPN_InvokeDefault(): WebKitPluginProcess killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Christian Stadelmann <fedora>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: dixontop, fedora, fmuellner, gleidson, hallo, iliketurtlesbro, invalid, jakub.skrzypnik, joshua.rich, kalevlember, krinkodot22, lray+redhatbugzilla, mcatanzaro+wrong-account-do-not-cc, miravetee, niki.guldbrand, otaylor, piette.simon, sgallagh, tpopela
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8addec22149d00218f6377a480c18d23cfd32461
Whiteboard: abrt_hash:b8b2021fde85f29f9b52c015ccd9109b7d4e58da
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-27 20:13:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Christian Stadelmann 2014-09-29 01:45:33 UTC
Version-Release number of selected component:
webkitgtk4-2.6.0-2.fc21

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/libexec/webkit2gtk-4.0/WebKitPluginProcess 22 /usr/lib64/mozilla/plugins/libgnome-shell-browser-plugin.so
crash_function: WebKit::NPN_InvokeDefault
executable:     /usr/libexec/webkit2gtk-4.0/WebKitPluginProcess
kernel:         3.16.3-302.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 WebKit::NPN_InvokeDefault at /usr/src/debug/webkitgtk-2.6.0/Source/WebKit2/WebProcess/Plugins/Netscape/NetscapeBrowserFuncs.cpp:686
 #1 on_shell_signal at browser-plugin.c:298
 #2 ffi_call_unix64 at ../src/x86/unix64.S:76
 #3 ffi_call at ../src/x86/ffi64.c:525
 #4 g_cclosure_marshal_generic at gclosure.c:1448
 #9 on_signal_received at gdbusproxy.c:917
 #10 emit_signal_instance_in_idle_cb at gdbusconnection.c:3753
 #15 WebKit::ChildProcessMain<WebKit::PluginProcess, WebKit::PluginProcessMain> at /usr/src/debug/webkitgtk-2.6.0/Source/WebKit2/Shared/unix/ChildProcessMain.h:61
 #17 _start

Comment 1 Christian Stadelmann 2014-09-29 01:45:37 UTC
Created attachment 942098 [details]
File: backtrace

Comment 2 Christian Stadelmann 2014-09-29 01:45:38 UTC
Created attachment 942099 [details]
File: cgroup

Comment 3 Christian Stadelmann 2014-09-29 01:45:39 UTC
Created attachment 942100 [details]
File: core_backtrace

Comment 4 Christian Stadelmann 2014-09-29 01:45:41 UTC
Created attachment 942101 [details]
File: dso_list

Comment 5 Christian Stadelmann 2014-09-29 01:45:42 UTC
Created attachment 942102 [details]
File: environ

Comment 6 Christian Stadelmann 2014-09-29 01:45:43 UTC
Created attachment 942103 [details]
File: exploitable

Comment 7 Christian Stadelmann 2014-09-29 01:45:44 UTC
Created attachment 942104 [details]
File: limits

Comment 8 Christian Stadelmann 2014-09-29 01:45:46 UTC
Created attachment 942105 [details]
File: maps

Comment 9 Christian Stadelmann 2014-09-29 01:45:47 UTC
Created attachment 942106 [details]
File: open_fds

Comment 10 Christian Stadelmann 2014-09-29 01:45:48 UTC
Created attachment 942107 [details]
File: proc_pid_status

Comment 11 Christian Stadelmann 2014-09-29 01:45:49 UTC
Created attachment 942108 [details]
File: var_log_messages

Comment 12 Stephen Gallagher 2014-10-01 12:30:33 UTC
Another user experienced a similar problem:

I tried to upgrade the World Clock extension at extensions.gnome.org using GNOME Web.

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/libexec/webkit2gtk-4.0/WebKitPluginProcess 15 /usr/lib64/mozilla/plugins/libgnome-shell-browser-plugin.so
crash_function: WebKit::NPN_InvokeDefault
executable:     /usr/libexec/webkit2gtk-4.0/WebKitPluginProcess
kernel:         3.16.3-301.fc21.x86_64
package:        webkitgtk4-2.6.0-2.fc21
reason:         WebKitPluginProcess killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            13041

Comment 13 Christian Stadelmann 2014-10-04 17:28:03 UTC
Another user experienced a similar problem:

I surfed on extensions.gnome.org using epiphany.

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/libexec/webkit2gtk-4.0/WebKitPluginProcess 27 /usr/lib64/mozilla/plugins/libgnome-shell-browser-plugin.so
crash_function: WebKit::NPN_InvokeDefault
executable:     /usr/libexec/webkit2gtk-4.0/WebKitPluginProcess
kernel:         3.16.3-302.fc21.x86_64
package:        webkitgtk4-2.6.0-2.fc21
reason:         WebKitPluginProcess killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 14 Tomas Popela 2015-01-28 08:28:08 UTC
*** Bug 1021245 has been marked as a duplicate of this bug. ***

Comment 15 Michael Catanzaro 2015-07-16 23:33:48 UTC
*** Bug 1244024 has been marked as a duplicate of this bug. ***

Comment 16 Michael Catanzaro 2015-09-27 16:51:34 UTC
*** Bug 1218373 has been marked as a duplicate of this bug. ***

Comment 17 Michael Catanzaro 2015-09-27 16:52:02 UTC
*** Bug 1266706 has been marked as a duplicate of this bug. ***

Comment 18 Joshua Rich 2015-11-04 11:36:24 UTC
Another user experienced a similar problem:

1. Opened https://extensions.gnome.org/local/ in Epiphany. 
2. Clicked "Upgrade this extension" button on out-of-date extension.  
3. Upgrade button disappears, extension remains same version, Epiphany doesn't crash. Abrt reports this crash.

reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/libexec/webkit2gtk-4.0/WebKitPluginProcess 24 /usr/lib64/mozilla/plugins/libgnome-shell-browser-plugin.so
crash_function: WebKit::NPN_InvokeDefault
executable:     /usr/libexec/webkit2gtk-4.0/WebKitPluginProcess
global_pid:     3890
kernel:         4.2.3-300.fc23.x86_64
package:        webkitgtk4-2.10.2-1.fc23
reason:         WebKitPluginProcess killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 19 Jens Lody 2015-11-16 09:45:54 UTC
Another user experienced a similar problem:

Accessing  extensions.gnome.org with epiphany looks good.
The crash appears after adding a new extension or enabling an already existing extension via the website.
See also : https://bugzilla.redhat.com/show_bug.cgi?id=1282373

reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/libexec/webkit2gtk-4.0/WebKitPluginProcess 23 /usr/lib64/mozilla/plugins/libgnome-shell-browser-plugin.so
crash_function: WebKit::NPN_InvokeDefault
executable:     /usr/libexec/webkit2gtk-4.0/WebKitPluginProcess
global_pid:     3789
kernel:         4.2.6-300.fc23.x86_64
package:        webkitgtk4-2.10.4-1.fc23
reason:         WebKitPluginProcess killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 20 Michael Catanzaro 2015-11-16 15:53:37 UTC
*** Bug 1281919 has been marked as a duplicate of this bug. ***

Comment 21 Michael Catanzaro 2015-11-17 19:22:01 UTC
OK, should be fixed in gnome-shell 3.18.3, whenever that comes out, hopefully for real this time. That should also fix the Firefox crashes introduced in 3.18.2 when trying to fix the plugin in WebKit. Also, the state inconsistencies when a shell extension is improperly reported as enabled or disabled should be fixed. See the GNOME bug for details.

Comment 22 Michael Catanzaro 2016-07-09 18:42:25 UTC
*** Bug 1350518 has been marked as a duplicate of this bug. ***

Comment 23 Michael Catanzaro 2016-07-09 18:44:41 UTC
(In reply to Michael Catanzaro from comment #21)
> OK, should be fixed in gnome-shell 3.18.3, whenever that comes out,
> hopefully for real this time. That should also fix the Firefox crashes
> introduced in 3.18.2 when trying to fix the plugin in WebKit. Also, the
> state inconsistencies when a shell extension is improperly reported as
> enabled or disabled should be fixed. See the GNOME bug for details.

Seems we're still getting new reports of this. :(

Comment 24 Michael Catanzaro 2016-07-09 18:45:51 UTC
*** Bug 1347940 has been marked as a duplicate of this bug. ***

Comment 25 Fedora End Of Life 2016-11-24 11:14:41 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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.

Comment 26 Fedora End Of Life 2016-12-20 12:54:47 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.

Comment 27 Michael Catanzaro 2017-08-31 04:56:25 UTC
*** Bug 1446881 has been marked as a duplicate of this bug. ***

Comment 28 Jakub Skrzypnik 2017-10-08 23:04:14 UTC
Similar problem has been detected:

Using Epiphany to install GNOME Extensions (the only purpose of this browser, since chrome-google-shell connectior doesn't work properly) got me this issue.

I've opened a few tabs with popular GNOME Shell extensions, and after toggling "ON" switch on a first one, the webkit crash happened.

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/libexec/webkit2gtk-4.0/WebKitPluginProcess 12 /usr/lib64/mozilla/plugins/libgnome-shell-browser-plugin.so
crash_function: WebKit::NPN_InvokeDefault
executable:     /usr/libexec/webkit2gtk-4.0/WebKitPluginProcess
journald_cursor: s=fdd7e100894c4d32bff86cb10cc564b1;i=30f9;b=2b415f252b314b45a48ac7c671fc1d97;m=159d904a3;t=55b10b18fb8af;x=54b5df59ee3158a9
kernel:         4.13.4-200.fc26.x86_64
package:        webkitgtk4-2.18.0-1.fc26
reason:         WebKitPluginProcess killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 29 Tomas Popela 2017-11-10 05:29:52 UTC
*** Bug 1511708 has been marked as a duplicate of this bug. ***

Comment 30 Tomas Popela 2017-11-10 05:29:54 UTC
*** Bug 1504972 has been marked as a duplicate of this bug. ***

Comment 31 Tomas Popela 2018-01-02 08:44:40 UTC
*** Bug 1529641 has been marked as a duplicate of this bug. ***

Comment 32 Tomas Popela 2018-03-19 05:09:20 UTC
*** Bug 1557683 has been marked as a duplicate of this bug. ***

Comment 33 Ben Cotton 2018-11-27 16:35:14 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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.

Comment 34 Ben Cotton 2018-11-30 20:28:53 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.

Comment 35 Tomas Popela 2018-12-03 05:53:11 UTC
*** Bug 1655342 has been marked as a duplicate of this bug. ***

Comment 36 Ben Cotton 2019-10-31 20:22:41 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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.

Comment 37 Ben Cotton 2019-11-27 20:13:00 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.