[Bug 1825197] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1825197/+attachment/5256636/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825197/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825197] Re: system unresponse for several seconds a couple of times per hour [Attempting to call back into JSAPI during the sweeping phase of GC...]
apport information ** Tags added: apport-collected third-party-packages ** Description changed: 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
[Bug 1825197] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1825197/+attachment/5256638/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825197/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825197] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1825197/+attachment/5256637/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825197/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825197] Re: system unresponse for several seconds a couple of times per hour [Attempting to call back into JSAPI during the sweeping phase of GC...]
Thanks for the feedback! I just send in the report collected by apport-collect, hope it helps. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825197/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825197] [NEW] system unresponse for several seconds a couple of times per hour
Public bug reported: 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
