GNOME Bugzilla – Bug 776993
High Glade CPU usage when Glade is not the focused application
Last modified: 2017-10-05 08:15:27 UTC
When using Glade on the GNOME desktop and then switching the focus to a different application window the CPU usage for Glade spikes very high and stays high until focus returns to Glade. When the Glade application window is focused its CPU usage returns to "normal". System: Linux magnum 4.8.15-300.fc25.x86_64 #1 SMP Thu Dec 15 23:10:23 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux GNOME Version 3.22.2
I am also seeing the Xorg process spike in CPU usage along with the CPU usage spike of Glade.
I have found that the high CPU usage for Glade and Xorg only happen if there are some widgets added to the workspace. The condition does not occur when Glade is opened to an empty workspace and left empty.
Also, not seeing the issue on a system which is using wayland instead of X
I can confirm this on Fedora 25 with Xfce on X11. I would question whether it only occurs when Glade lacks focus, however. My figures on an i3-530 are 98% Xorg usage and 12% Glade usage when lacking focus, 8% Glade usage when focused.
Same thing on up-to-date debian testing. Some terminal output is here (bug #778643). Let me know what else I can do to help with this issue. Thanks.
No idea if this is the same bug, but I get the same behaviour (high CPU load from glade and X11) when adding a Stack with a StackSwitcher, even when Glade is focused. I did some debugging, seems like something causes expose events to be emitted continuously.
Could it be related to https://bugzilla.gnome.org/show_bug.cgi?id=763624 ? Try the master branch of Glade from Git, or apply this commit in your branch: https://github.com/GNOME/glade/commit/ac55fa78566145ac44d48ba88ec1351db5b4a99d Cheers
(In reply to Arnaud Rebillout from comment #7) > Could it be related to https://bugzilla.gnome.org/show_bug.cgi?id=763624 ? > > Try the master branch of Glade from Git, or apply this commit in your branch: Thanks for pointing this out, indeed this has to be a duplicate. *** This bug has been marked as a duplicate of bug 763624 ***