** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Summary changed:
- system unresponse for several seconds a couple of times per hour [Attempting
to call back into JSAPI during the sweeping phase of GC...]
+ system unresponse for several seconds a couple of times per hour [Attempting
to call back into JSAPI during the sweeping phase of GC... The offending signal
was g-signal on GDBusProxy]
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1825197
Title:
system unresponse for several seconds a couple of times per hour
[Attempting to call back into JSAPI during the sweeping phase of GC...
The offending signal was g-signal on GDBusProxy]
Status in gnome-shell package in Ubuntu:
New
Bug description:
My system is up-to-date on:
$ lsb_release -rd
Description: Ubuntu 18.10
Release: 18.10
$ apt-cache policy gnome-shell
gnome-shell:
Installed: 3.30.2-0ubuntu1.18.10.1
Candidate: 3.30.2-0ubuntu1.18.10.1
To provide you with an idea of the motivation for the origin in gnome-
shell; I've included the lines in syslog that are displayed for many
more occasions than presented below.
At the times that these messages are displayed in my logs I can still
move my mouse, but mouse clicks are unresponsive and typing is frozen
(but text does appear after freeze).
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into
JSAPI during the sweeping phase of GC. This is most likely caused by not
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but
can also be caused by using the destroy(), dispose(), or remove() vfuncs.
Because it would crash the application, it has been blocked and the JS callback
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was
g-signal on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into
JSAPI during the sweeping phase of GC. This is most likely caused by not
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but
can also be caused by using the destroy(), dispose(), or remove() vfuncs.
Because it would crash the application, it has been blocked and the JS callback
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was
g-signal on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into
JSAPI during the sweeping phase of GC. This is most likely caused by not
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but
can also be caused by using the destroy(), dispose(), or remove() vfuncs.
Because it would crash the application, it has been blocked and the JS callback
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was
g-signal on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into
JSAPI during the sweeping phase of GC. This is most likely caused by not
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but
can also be caused by using the destroy(), dispose(), or remove() vfuncs.
Because it would crash the application, it has been blocked and the JS callback
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was
g-signal on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into
JSAPI during the sweeping phase of GC. This is most likely caused by not
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but
can also be caused by using the destroy(), dispose(), or remove() vfuncs.
Because it would crash the application, it has been blocked and the JS callback
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was
g-signal on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into
JSAPI during the sweeping phase of GC. This is most likely caused by not
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but
can also be caused by using the destroy(), dispose(), or remove() vfuncs.
Because it would crash the application, it has been blocked and the JS callback
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was
g-signal on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into
JSAPI during the sweeping phase of GC. This is most likely caused by not
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but
can also be caused by using the destroy(), dispose(), or remove() vfuncs.
Because it would crash the application, it has been blocked and the JS callback
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was
g-signal on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into
JSAPI during the sweeping phase of GC. This is most likely caused by not
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but
can also be caused by using the destroy(), dispose(), or remove() vfuncs.
Because it would crash the application, it has been blocked and the JS callback
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was
g-signal on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into
JSAPI during the sweeping phase of GC. This is most likely caused by not
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but
can also be caused by using the destroy(), dispose(), or remove() vfuncs.
Because it would crash the application, it has been blocked and the JS callback
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was
g-signal on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into
JSAPI during the sweeping phase of GC. This is most likely caused by not
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but
can also be caused by using the destroy(), dispose(), or remove() vfuncs.
Because it would crash the application, it has been blocked and the JS callback
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2019-03-07 (41 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
Package: gnome-shell 3.30.2-0ubuntu1.18.10.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
Tags: cosmic third-party-packages
Uname: Linux 4.18.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825197/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
