Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#70529 - [gnome-shell][glib2] High CPU usage since update to GNOME 40

Attached to Project: Arch Linux
Opened by Jonas Hahnfeld (hahnjo) - Wednesday, 21 April 2021, 17:33 GMT
Last edited by David Thurstenson (thurstylark) - Wednesday, 23 March 2022, 19:32 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Since a few days (I think coinciding with the update to GNOME 40), gnome-shell starts to use 100% (one core) after a while. When attaching with gdb and running "thread apply all bt", I see that the LWP of the one "pool-gnome-shel" thread is steadily increasing (spawning and killing them, I suppose). The stack trace is:
#0 0x00007f3a8e1dba9d in syscall () at /usr/lib/
#1 0x00007f3a8eff106b in g_cond_wait_until () at /usr/lib/
#2 0x00007f3a8ef728b3 in () at /usr/lib/
#3 0x00007f3a8ef72a44 in g_async_queue_timeout_pop () at /usr/lib/
#4 0x00007f3a8efd3d2a in () at /usr/lib/
#5 0x00007f3a8efd10c1 in () at /usr/lib/
#6 0x00007f3a8d71f299 in start_thread () at /usr/lib/
#7 0x00007f3a8e1e1053 in clone () at /usr/lib/

Additional info:
* gnome-shell 1:40.0+39+gd9e953e93-1
* glib2 2.68.1-1
* on i915, running Wayland

Steps to reproduce:
Just wait. Maybe it's related that I suspend my laptop multiple times a day.
This task depends upon

Closed by  David Thurstenson (thurstylark)
Wednesday, 23 March 2022, 19:32 GMT
Reason for closing:  Fixed
Comment by Jonas Hahnfeld (hahnjo) - Wednesday, 21 April 2021, 17:54 GMT
Immediately after reporting, I had the idea to attach strace and I see the same sequence of ioctl's repeated over and over again. I've reported upstream.
Comment by mattia (nTia89) - Sunday, 20 March 2022, 15:27 GMT
I cannot reproduce the issue. Is it still valid for you?
Comment by Jonas Hahnfeld (hahnjo) - Sunday, 20 March 2022, 16:38 GMT
No, as written in the upstream bug report I didn't run into this since last year May. Sorry for not updating this (downstream) bug report.