After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 778498 - gnome-shell running busy loop (100% CPU load on one core) in main thread with nothing to do
gnome-shell running busy loop (100% CPU load on one core) in main thread with...
Status: RESOLVED OBSOLETE
Product: gnome-shell
Classification: Core
Component: general
3.22.x
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-02-11 17:34 UTC by Christian Stadelmann
Modified: 2021-07-05 14:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
A backtrace from running `t a a bt full` in gdb attached to gnome-shell (13.78 KB, text/plain)
2017-02-11 17:34 UTC, Christian Stadelmann
Details
excerpt from syslog. Bug manifested before 18:22. (10.96 KB, text/plain)
2017-02-11 17:39 UTC, Christian Stadelmann
Details

Description Christian Stadelmann 2017-02-11 17:34:09 UTC
Created attachment 345530 [details]
A backtrace from running `t a a bt full` in gdb attached to gnome-shell

I am running a GNOME session on wayland in Fedora 25. I do not have any extensions enabled.

Steps to reproduce:
unclear.
I did however do this before I noticed the bug:
* I suspended the computer (at least twice)
* I enabled and then disabled the "system-monitor" gnome-shell-extension [1]

What happens:
Busy loop in main thread on one CPU core. gdb reveals that it happens in this piece of code:
Thread 1 "gnome-shell" received signal SIGINT, Interrupt.
0x00007fc2f91ea01d in poll () at ../sysdeps/unix/syscall-template.S:84
84	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
  • #0 poll
    at ../sysdeps/unix/syscall-template.S line 84
  • #1 g_main_context_poll
    at gmain.c line 4228
  • #2 g_main_context_iterate
    at gmain.c line 3924
  • #3 g_main_loop_run
    at gmain.c line 4125
  • #4 meta_run
    at core/main.c line 572
  • #5 main
    at main.c line 471

What should happen:
No busy loop.

Additional info:
As soon as I switch to tty, gnome-shell CPU usage goes down to zero. It immediately goes back to 100% on one core when I switch back to the gnome/wayland session.

Software versions in use:
gnome-shell-3.22.2-2.fc25.x86_64
libwayland-client-1.12.0-1.fc25.x86_64
clutter-1.26.0-1.fc25.x86_64
mutter-3.22.2-3.fc25.x86_64
glib2-2.50.2-1.fc25.x86_64
gtk3-3.22.7-1.fc25.x86_64
kernel 4.9.8-201.fc25.x86_64
GPU: Intel HD Graphics (Clarkdale)
Fedora 25

[1] https://github.com/elvetemedve/gnome-shell-extension-system-monitor
Comment 1 Christian Stadelmann 2017-02-11 17:39:55 UTC
Created attachment 345531 [details]
excerpt from syslog. Bug manifested before 18:22.
Comment 2 GNOME Infrastructure Team 2021-07-05 14:35:21 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of  gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/

Thank you for your understanding and your help.