gnome-shell-extension-appindicator
gnome-shell-extension-appindicator copied to clipboard
Published
20 hours ago •
ubuntu
ubuntu
gnome-shell 99% cpu usage and desktop unresponsive
When this extension is enabled, I can consistently soft freeze my desktop with gnome-shell taking all CPU for minutes when performing certain actions. Same actions with this extension disabled do not produce high gnome-shell cpu usage
I saw the same problem on Fedora 30 an 31. Reproduced today with system up to date. I am under a X session
This can be clearly reproduced the following way :
- With virt-manager while connecting to a remote host (libvirt tcp remote connection) with a lot of guests (because cpu usage ramp up takes a few seconds). During the time that each virtual machine is enumerated, the desktop is unresponsive.
I see a lot of :
nov. 20 15:19:18 sheepora-X230 gnome-shell[3300]: [AppIndicatorSupport-WARN] Attempting to re-register :1.5108/org/ayatana/NotificationItem/virt_manager; resetting instead
nov. 20 15:19:18 sheepora-X230 gnome-shell[3300]: [AppIndicatorSupport-WARN] Item :1.5108/org/ayatana/NotificationItem/virt_manager is already registered
nov. 20 15:19:19 sheepora-X230 gnome-shell[3300]: [AppIndicatorSupport-WARN] Attempting to re-register :1.5108/org/ayatana/NotificationItem/virt_manager; resetting instead
nov. 20 15:19:19 sheepora-X230 gnome-shell[3300]: [AppIndicatorSupport-WARN] Item :1.5108/org/ayatana/NotificationItem/virt_manager is already registered
...
...
This also often happened to me on Manjaro (GNOME edition). I did not experience any more freezes after disabling the extension.
This has happened to me too. I believe it might be because of Discord, at least in my case: whenever I was connected to a call, the issue arose.
I didn't have discord installed which leads me to believe that there is an issue with the extension and not the apps themselves.
Just tried latest master but the problem persists.
I do not see errors in log anymore but, with the extension active gnome-shell CPU usage is at 100% during remote VMs enumeration by virt-manager (this takes about 2min with ~50vm, that's why it's easily noticeable and replicable). The whole desktop gets extremely unresponsive.
CPU stays under 2% with this extension disabled and performing the same action.
Mh, weird... Could you maybe run gnome-shell with G_MESSAGES_DEBUG=all env set and attach the journalctl /usr/bin/gnome-shell -b0 result when virt-manager causes this?
Also not familiar with that, is it virtual-manager status notification icon updating a lot during such process?
How should I run gnome-shell with debug? I tried to add "Environment=G_MESSAGES_DEBUG=all" to gdm.service and restart session but that does not show anything more in journalctl
virtual-manager's icon is static during the process but when clicking on it there is a menu listing the vm available for each QEMU connection that gets populated as vm are enumerated :
Oh, so it's the menu addition that causes problems... Maybe having a dump of that dbus-menu could be useful to be able to reproduce the issue.
However, if it's not icon related, I'm quite sure the problem we've here is exactly the same of https://gitlab.gnome.org/GNOME/gnome-shell/issues/1576
Anyways, to set the environment you should change instead /usr/lib/systemd/user/gnome-shell-x11.service or /usr/lib/systemd/user/gnome-shell-wayland.service
Launching virt-manager :
mars 14 17:39:18 sheepora-X230 [email protected][1803]: Registering StatusNotifierItem :1.93/org/ayatana/NotificationItem/virt_manager
mars 14 17:39:18 sheepora-X230 [email protected][1803]: Attempting to re-register :1.93/org/ayatana/NotificationItem/virt_manager; resetting instead
mars 14 17:39:18 sheepora-X230 [email protected][1803]: virt-manager, Icon virt-manager@16 Is still loading, ignoring the request
mars 14 17:39:18 sheepora-X230 [email protected][1803]: virt-manager, Icon virt-manager@16 Is still loading, ignoring the request
mars 14 17:39:18 sheepora-X230 [email protected][1803]: virt-manager, Icon virt-manager@16 Is still loading, ignoring the request
mars 14 17:39:18 sheepora-X230 [email protected][1803]: virt-manager, Icon virt-manager@16 Is still loading, ignoring the request
mars 14 17:39:18 sheepora-X230 [email protected][1803]: virt-manager, Icon virt-manager@16 Is still loading, ignoring the request
mars 14 17:39:18 sheepora-X230 [email protected][1803]: virt-manager, Icon virt-manager@16 Is still loading, ignoring the request
mars 14 17:39:18 sheepora-X230 [email protected][1803]: Attempting to re-register :1.93/org/ayatana/NotificationItem/virt_manager; resetting instead
mars 14 17:39:18 sheepora-X230 [email protected][1803]: virt-manager, Icon virt-manager@16 Is still loading, ignoring the request
mars 14 17:39:18 sheepora-X230 [email protected][1803]: IconCache: adding virt-manager@16
mars 14 17:39:18 sheepora-X230 [email protected][1803]: IconCache: garbage collector started
mars 14 17:39:20 sheepora-X230 [email protected][1803]: Attempting to re-register :1.93/org/ayatana/NotificationItem/virt_manager; resetting instead
mars 14 17:39:20 sheepora-X230 [email protected][1803]: IconCache: removing virt-manager@16
mars 14 17:39:20 sheepora-X230 [email protected][1803]: IconCache: garbage collector stopped
mars 14 17:39:20 sheepora-X230 [email protected][1803]: IconCache: adding virt-manager@16
mars 14 17:39:20 sheepora-X230 [email protected][1803]: IconCache: garbage collector started
mars 14 17:39:31 sheepora-X230 [email protected][1803]: IconCache: virt-manager@16 is in use.
mars 14 17:39:41 sheepora-X230 [email protected][1803]: IconCache: virt-manager@16 is in use.
Then connecting to a remote QEMU/KVM hosts, where the high resource usage is observed :
mars 14 17:40:20 sheepora-X230 [email protected][1803]: Attempting to re-register :1.93/org/ayatana/NotificationItem/virt_manager; resetting instead
mars 14 17:40:20 sheepora-X230 [email protected][1803]: IconCache: removing virt-manager@16
mars 14 17:40:20 sheepora-X230 [email protected][1803]: IconCache: garbage collector stopped
mars 14 17:40:20 sheepora-X230 [email protected][1803]: IconCache: adding virt-manager@16
mars 14 17:40:20 sheepora-X230 [email protected][1803]: IconCache: garbage collector started
mars 14 17:40:21 sheepora-X230 [email protected][1803]: Attempting to re-register :1.93/org/ayatana/NotificationItem/virt_manager; resetting instead
mars 14 17:40:21 sheepora-X230 [email protected][1803]: IconCache: removing virt-manager@16
mars 14 17:40:21 sheepora-X230 [email protected][1803]: IconCache: garbage collector stopped
mars 14 17:40:21 sheepora-X230 [email protected][1803]: IconCache: adding virt-manager@16
mars 14 17:40:21 sheepora-X230 [email protected][1803]: IconCache: garbage collector started
mars 14 17:40:22 sheepora-X230 [email protected][1803]: Attempting to re-register :1.93/org/ayatana/NotificationItem/virt_manager; resetting instead
mars 14 17:40:22 sheepora-X230 [email protected][1803]: IconCache: removing virt-manager@16
mars 14 17:40:22 sheepora-X230 [email protected][1803]: IconCache: garbage collector stopped
mars 14 17:40:22 sheepora-X230 [email protected][1803]: IconCache: adding virt-manager@16
mars 14 17:40:22 sheepora-X230 [email protected][1803]: IconCache: garbage collector started
mars 14 17:40:24 sheepora-X230 [email protected][1803]: Attempting to re-register :1.93/org/ayatana/NotificationItem/virt_manager; resetting instead
mars 14 17:40:24 sheepora-X230 [email protected][1803]: IconCache: removing virt-manager@16
mars 14 17:40:24 sheepora-X230 [email protected][1803]: IconCache: garbage collector stopped
mars 14 17:40:24 sheepora-X230 [email protected][1803]: IconCache: adding virt-manager@16
mars 14 17:40:24 sheepora-X230 [email protected][1803]: IconCache: garbage collector started
mars 14 17:40:25 sheepora-X230 [email protected][1803]: Attempting to re-register :1.93/org/ayatana/NotificationItem/virt_manager; resetting instead
mars 14 17:40:25 sheepora-X230 [email protected][1803]: IconCache: removing virt-manager@16
mars 14 17:40:25 sheepora-X230 [email protected][1803]: IconCache: garbage collector stopped
mars 14 17:40:25 sheepora-X230 [email protected][1803]: IconCache: adding virt-manager@16
mars 14 17:40:25 sheepora-X230 [email protected][1803]: IconCache: garbage collector started
mars 14 17:40:26 sheepora-X230 [email protected][1803]: Attempting to re-register :1.93/org/ayatana/NotificationItem/virt_manager; resetting instead
mars 14 17:40:26 sheepora-X230 [email protected][1803]: IconCache: removing virt-manager@16
mars 14 17:40:26 sheepora-X230 [email protected][1803]: IconCache: garbage collector stopped
...
...
...
I experience the same issue with virt-manager and it's notification icon. I have disabled the icon in virt-manager, and the problem goes away.
The problem manifests itself with gnome-shell taking 100% of it's CPU core and the whole UI being basically stalled.
I'm on Ubuntu 19.10, nothing custom, all updated, Xorg and nvidia binary drivers.
It's getting worse
I retried today on fedora 32 up2date with latest appindicator release. After the usual slow ramp up of cpu usage by gnome-shell, It now completely freezes/locks the gnome session when reaching 100%.
Will try to replicate this again, but it's a bit hard so far.. I need a way to easily populate my virt-manager with lots of images it seems :)
Could you please check if applying this improves the things?
It should be just enough to change it to the files you've installed in /usr/share/gnome-shell/extensions/ or in ~/.local/share/gnome-shell/extensions
diff --git a/appIndicator.js b/appIndicator.js
index 46c2d41..0c86e30 100644
--- a/appIndicator.js
+++ b/appIndicator.js
@@ -179,6 +179,7 @@ var AppIndicator = class AppIndicators_AppIndicator {
}
_onProxySignal(_proxy, _sender, signal, _params) {
+ this._cancelReset();
this._accumuledSignals.add(signal);
if (this._signalsAccumulatorId)
@@ -282,7 +283,21 @@ var AppIndicator = class AppIndicators_AppIndicator {
}
reset() {
- this.emit('reset');
+ if (this._resetTimeout)
+ return;
+
+ this._resetTimeout = GLib.timeout_add(
+ GLib.PRIORITY_DEFAULT_IDLE, MAX_UPDATE_FREQUENCY, () => {
+ delete this._resetTimeout;
+ this.emit('reset');
+ });
+ }
+
+ _cancelReset() {
+ if (this._resetTimeout) {
+ GLib.Source.remove(this._resetTimeout);
+ delete this._resetTimeout;
+ }
}
destroy() {
@@ -299,6 +314,8 @@ var AppIndicator = class AppIndicators_AppIndicator {
delete this._signalsAccumulatorId;
}
+ this._cancelReset()
+
if (this._delayCheck) {
GLib.Source.remove(this._delayCheck);
delete this._delayCheck;
I understand that replicating is not easy ;p You need to connect to a remote libvirt connection, as the induced latency seems to be involved. As described, I connect to a remote KVM hosts with libvirt over TCP. And to make matter worse, I'm in Japan and the KVM host is in France, so there's a ~250ms round trip.
I'm testing your patch, will report
I see thouthands of the following repeating lines in journal :
...
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: == Stack trace for context 0x5603c9f95ad0 ==
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: == Stack trace for context 0x5603c9f95ad0 ==
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: == Stack trace for context 0x5603c9f95ad0 ==
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: The offending callback was SourceFunc().
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: == Stack trace for context 0x5603c9f95ad0 ==
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: == Stack trace for context 0x5603c9f95ad0 ==
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(),>
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: == Stack trace for context 0x5603c9f95ad0 ==
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: == Stack trace for context 0x5603c9f95ad0 ==
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: The offending callback was SourceFunc().
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(),>
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: The offending callback was SourceFunc().
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(),>
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: The offending callback was SourceFunc().
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(),>
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(),>
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: The offending callback was SourceFunc().
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(),>
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: The offending callback was SourceFunc().
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: == Stack trace for context 0x5603c9f95ad0 ==
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: == Stack trace for context 0x5603c9f95ad0 ==
sept. 24 02:53:34 sheepora-X230 gnome-shell[7041]: == Stack trace for context 0x5603c9f95ad0 ==
...
Mh, try with this?
diff --git a/appIndicator.js b/appIndicator.js
index 46c2d41..5808ed8 100644
--- a/appIndicator.js
+++ b/appIndicator.js
@@ -179,6 +179,7 @@ var AppIndicator = class AppIndicators_AppIndicator {
}
_onProxySignal(_proxy, _sender, signal, _params) {
+ this._cancelReset();
this._accumuledSignals.add(signal);
if (this._signalsAccumulatorId)
@@ -282,7 +283,22 @@ var AppIndicator = class AppIndicators_AppIndicator {
}
reset() {
- this.emit('reset');
+ if (!this._proxy || this._resetTimeout)
+ return;
+
+ this._resetTimeout = GLib.timeout_add(
+ GLib.PRIORITY_DEFAULT_IDLE, MAX_UPDATE_FREQUENCY, () => {
+ delete this._resetTimeout;
+ this.emit('reset');
+ return GLib.SOURCE_REMOVE;
+ });
+ }
+
+ _cancelReset() {
+ if (this._resetTimeout) {
+ GLib.Source.remove(this._resetTimeout);
+ delete this._resetTimeout;
+ }
}
destroy() {
@@ -299,6 +315,8 @@ var AppIndicator = class AppIndicators_AppIndicator {
delete this._signalsAccumulatorId;
}
+ this._cancelReset()
+
if (this._delayCheck) {
GLib.Source.remove(this._delayCheck);
delete this._delayCheck;
This is what I get with your second patch :
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: 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>
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #0 7ffc5416d900 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:681 (378e8f98178 @ 284)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #1 7ffc5416d960 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:587 (378e8f95c40 @ 391)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #2 7ffc5416d9b0 I self-hosted:1013 (36ebf5b06c40 @ 492)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #3 7ffc5416da60 I resource:///org/gnome/gjs/modules/core/_signals.js:133 (378e8fb2da8 @ 427)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #4 7ffc5416dab0 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:126 (378e8f8f718 @ 68)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #5 7ffc5416db30 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:289 (378e8f95088 @ 379)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #6 7ffc5416db90 I self-hosted:266 (40b3547e790 @ 259)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #7 559a42d9fad0 i /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:283 (378e8f8ff88 @ 130)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #8 7ffc5416eda0 I self-hosted:1013 (36ebf5b06c40 @ 492)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #9 559a42d9fa18 i resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (181aae9926a0 @ 312)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #0 7ffc5416d900 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:681 (378e8f98178 @ 284)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #1 7ffc5416d960 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:587 (378e8f95c40 @ 391)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #2 7ffc5416d9b0 I self-hosted:1013 (36ebf5b06c40 @ 492)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #3 7ffc5416da60 I resource:///org/gnome/gjs/modules/core/_signals.js:133 (378e8fb2da8 @ 427)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #4 7ffc5416dab0 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:126 (378e8f8f718 @ 68)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #5 7ffc5416db30 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:289 (378e8f95088 @ 379)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSubMenuMenuItem 0x559a44a30380.
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #6 7ffc5416db90 I self-hosted:266 (40b3547e790 @ 259)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #7 559a42d9fad0 i /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:283 (378e8f8ff88 @ 130)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #8 7ffc5416eda0 I self-hosted:1013 (36ebf5b06c40 @ 492)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #9 559a42d9fa18 i resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (181aae9926a0 @ 312)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #0 7ffc5416d900 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:681 (378e8f98178 @ 284)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #1 7ffc5416d960 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:587 (378e8f95c40 @ 391)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #2 7ffc5416d9b0 I self-hosted:1013 (36ebf5b06c40 @ 492)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #3 7ffc5416da60 I resource:///org/gnome/gjs/modules/core/_signals.js:133 (378e8fb2da8 @ 427)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #4 7ffc5416dab0 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:126 (378e8f8f718 @ 68)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: 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>
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #5 7ffc5416db30 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:289 (378e8f95088 @ 379)
...
...
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #0 7ffc5416d800 I resource:///org/gnome/shell/ui/popupMenu.js:224 (36ebf5b1b538 @ 70)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #1 7ffc5416d8c0 b resource:///org/gnome/shell/ui/popupMenu.js:1213 (36ebf5b20448 @ 25)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #2 7ffc5416d900 I resource:///org/gnome/shell/ui/popupMenu.js:238 (36ebf5b1b628 @ 60)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #3 7ffc5416d960 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:657 (378e8f98100 @ 41)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #4 7ffc5416d960 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:581 (378e8f95c40 @ 179)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #5 7ffc5416d9b0 I self-hosted:1013 (36ebf5b06c40 @ 492)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #6 7ffc5416da60 I resource:///org/gnome/gjs/modules/core/_signals.js:133 (378e8fb2da8 @ 427)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: The offending signal was notify on Gjs_ui_popupMenu_PopupMenuItem 0x559a44a51880.
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #7 7ffc5416dab0 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:126 (378e8f8f718 @ 68)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #8 7ffc5416db30 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:289 (378e8f95088 @ 379)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #9 7ffc5416db90 I self-hosted:266 (40b3547e790 @ 259)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #10 559a42d9fad0 i /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:283 (378e8f8ff88 @ 130)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #11 7ffc5416eda0 I self-hosted:1013 (36ebf5b06c40 @ 492)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #12 559a42d9fa18 i resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (181aae9926a0 @ 312)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: 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>
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: The offending signal was notify on Gjs_ui_popupMenu_PopupMenuItem 0x559a45ff51f0.
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: 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>
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: The offending signal was notify on Gjs_ui_popupMenu_PopupMenuItem 0x559a42f958d0.
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: 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>
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: The offending signal was notify on Gjs_ui_popupMenu_PopupMenuItem 0x559a46bd5ac0.
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: 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>
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: The offending signal was notify on Gjs_ui_popupMenu_PopupMenuItem 0x559a45eddd40.
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: 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>
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x559a46d88930.
...
...
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #0 7ffc5416d900 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:681 (378e8f98178 @ 284)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #1 7ffc5416d960 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:587 (378e8f95c40 @ 391)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #2 7ffc5416d9b0 I self-hosted:1013 (36ebf5b06c40 @ 492)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #3 7ffc5416da60 I resource:///org/gnome/gjs/modules/core/_signals.js:133 (378e8fb2da8 @ 427)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #4 7ffc5416dab0 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:126 (378e8f8f718 @ 68)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #5 7ffc5416db30 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:289 (378e8f95088 @ 379)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #6 7ffc5416db90 I self-hosted:266 (40b3547e790 @ 259)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #7 559a42d9fad0 i /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:283 (378e8f8ff88 @ 130)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSubMenuMenuItem 0x559a459743f0.
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #8 7ffc5416eda0 I self-hosted:1013 (36ebf5b06c40 @ 492)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #9 559a42d9fa18 i resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (181aae9926a0 @ 312)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #0 7ffc5416d900 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:681 (378e8f98178 @ 284)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #1 7ffc5416d960 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:587 (378e8f95c40 @ 391)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #2 7ffc5416d9b0 I self-hosted:1013 (36ebf5b06c40 @ 492)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #3 7ffc5416da60 I resource:///org/gnome/gjs/modules/core/_signals.js:133 (378e8fb2da8 @ 427)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #4 7ffc5416dab0 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:126 (378e8f8f718 @ 68)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #5 7ffc5416db30 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:289 (378e8f95088 @ 379)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #6 7ffc5416db90 I self-hosted:266 (40b3547e790 @ 259)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #7 559a42d9fad0 i /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:283 (378e8f8ff88 @ 130)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #8 7ffc5416eda0 I self-hosted:1013 (36ebf5b06c40 @ 492)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #9 559a42d9fa18 i resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (181aae9926a0 @ 312)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #0 7ffc5416d900 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:681 (378e8f98178 @ 284)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #1 7ffc5416d960 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:587 (378e8f95c40 @ 391)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #2 7ffc5416d9b0 I self-hosted:1013 (36ebf5b06c40 @ 492)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #3 7ffc5416da60 I resource:///org/gnome/gjs/modules/core/_signals.js:133 (378e8fb2da8 @ 427)
sept. 24 14:40:52 sheepora-X230 gnome-shell[12835]: #4 7ffc5416dab0 I /home/sheepdestroyer/.local/share/gnome-shell/extensions/[email protected]/dbusMenu.js:126 (378e8f8f718 @ 68)
...
...
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy()>
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: The offending callback was SourceFunc().
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy()>
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: The offending callback was SourceFunc().
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy()>
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
sept. 24 14:41:24 sheepora-X230 gnome-shell[12835]: == Stack trace for context 0x559a3e721a80 ==
...
...
Mh, still trying to figure out, as I can't get that in my-stress-test indicator...
However, a part the errors, the CPU usage is still high, right?
I'd look also in virt-manager itself though, as for what I see it disposes and recreates the same indicator multiple times, and this doesn't look correct.
Yes, gnome-shell's CPU usage is still at 100% after a while, then the session freezes soon after
This may also have the effect that unlocking the screen with this extensions takes some seconds. Together with other slow extensions unlocking the screen takes nearly 15s on my system.
It may be related to the findings of this (very interesting) thread from @mildsunrise in https://twitter.com/mild_sunrise/status/1458739604098621443
I`m facing the same problem using the virt-manager
Need to disable this extension!
