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 683204 - GNOME Shell has high CPU consumption in 'Activities' view
GNOME Shell has high CPU consumption in 'Activities' view
Status: RESOLVED OBSOLETE
Product: gnome-shell
Classification: Core
Component: general
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-09-02 13:42 UTC by Luca Wehrstedt
Modified: 2021-07-05 14:34 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
The gdb backtrace (24.80 KB, text/plain)
2012-09-02 13:42 UTC, Luca Wehrstedt
Details
The gdb backtrace (24.57 KB, text/plain)
2012-09-02 19:29 UTC, Luca Wehrstedt
Details

Description Luca Wehrstedt 2012-09-02 13:42:29 UTC
Created attachment 223199 [details]
The gdb backtrace

When switching to Activities view the CPU suddenly jumps to about 70% to 100%. It again suddenly stops when closing the view. A open terminal with top running says it's gnome-shell's fault. Yet, the Shell doesn't seem to get any slower or to hang. I got a gdb backtrace while this happens (actually, I got three of them but they're identical so I'm attaching just one).

I'm running a Gentoo AMD64 system (with testing packages enabled) with Nouveau graphics drivers.
Comment 1 Jasper St. Pierre (not reading bugmail) 2012-09-02 18:20:15 UTC
The backtrace is meaningless. It basically says that the shell is waiting for the X server to reply, and that's it.
Comment 2 Jasper St. Pierre (not reading bugmail) 2012-09-02 18:21:19 UTC
Oh, did you switch to a VT to take that backtrace? That would mean that the X server is not replying to clients, because it's waiting to take the DRM lock again.
Comment 3 Luca Wehrstedt 2012-09-02 18:26:12 UTC
Yes, I did. I tried to do it using a gnome-terminal but it froze the entire X server and I had to switch to a VT to kill gdb. How can I get a useful backtrace?
Comment 4 Jasper St. Pierre (not reading bugmail) 2012-09-02 18:36:17 UTC
ssh in with another system
Comment 5 Luca Wehrstedt 2012-09-02 19:29:31 UTC
Created attachment 223211 [details]
The gdb backtrace

Ok, I did that. I got 10 backtraces. One is (incidentally?) the same as the ones before. Yet, I got another one very frequently (7 times out of 10). I'm attaching it. If you also need the other 2 backtraces I got just tell me and I'll attach them too.
Comment 6 GNOME Infrastructure Team 2021-07-05 14:34:57 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.