Bug 1369409

Summary: High gnome-shell CPU usage
Product: [Fedora] Fedora Reporter: John Levon <levon>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 24CC: fmuellner, otaylor, wberrier
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 16:41:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description John Levon 2016-08-23 10:35:47 UTC
Description of problem:

Using current F24 gnome-shell, gnome-shell is eating CPU. It varies but often is at 80%. A strace shows it's getting EAGAIN on a couple of sockets and futexes...

read(4, 0x7ffd9564db30, 16)             = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(5, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
...

lrwx------ 1 moz moz 64 Aug 23 11:31 /proc/26844/fd/4 -> 'anon_inode:[eventfd]'
[moz@pent ~]$ ls -l /proc/26844/fd/5
lrwx------ 1 moz moz 64 Aug 23 11:19 /proc/26844/fd/5 -> 'socket:[27501176]'


This is similar to a previous bug about the background extension, but that doesn't seem to exist any more, and setting background to "None" makes no difference.

I do have two monitor configuration.

journalctl doesn't show anything for gnome/Xorg (I'm not using Wayland).
Nothing else is showing up in top

Alt-F2-r seems to reduce to the CPU usage, but it's still getting tons of EAGAIN.

Version-Release number of selected component (if applicable):

gnome-shell-3.20.3-3.fc24.x86_64

How reproducible:

All the time

Comment 1 Wade Berrier 2016-11-11 03:34:07 UTC
I'm also seeing high CPU usage on centos 7.2.

Name        : gnome-shell
Version     : 3.14.4
Release     : 37.el7

Is that appropriate to put on this bug report, or should another be opened?

Here's the video card:

01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev a1)

I'm using the nouveau driver (opposed to the nvidia binary driver).

But, I also see this on other video drivers as well.

Comment 2 Fedora End Of Life 2017-07-25 22:35:18 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-08-08 16:41:08 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.