Bug 1551990 - Significant CPU usage when moving mouse
Summary: Significant CPU usage when moving mouse
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1547691
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-06 10:01 UTC by Milan Crha
Modified: 2019-11-27 19:02 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-27 19:02:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Milan Crha 2018-03-06 10:01:37 UTC
This had been discovered within bug #1547691 comment #23:

Using gdm (which runs Wayland), just quickly moving mouse left-right above the grey area (where is nothing to click on) causes significant CPU usage. This is within a virtual machine. When I log in to the GNOME (Wayland), then `top` shows gnome-shell as the main CPU user when moving mouse around the desktop (where is also nothing to click on). Logging into GNOME on X.org also shows a bit higher CPU usage, but it's nothing that significant like under Wayland.

Fedora 27 seems to be also affected.

I do not think crazy mouse move should cause any such CPU usage, not talking that it causes high power consumption, thus less up time for the laptops on batteries.

Comment 1 Jonas Ådahl 2018-06-07 10:42:16 UTC
This was concluded to be a mesa issue right?

Comment 2 Milan Crha 2018-06-08 07:08:56 UTC
(In reply to Jonas Ådahl from comment #1)
> This was concluded to be a mesa issue right?

No idea from my side.

Comment 3 Jonas Ådahl 2018-06-08 08:39:16 UTC
Does it still reproduce for you?

Comment 4 alexnryndin 2018-06-08 10:18:09 UTC
It still reproduces on my Dell Latitude 5480 with latest gnome-shell (3.28.2). Up to 35% cpu usage when mouse moving.

Comment 5 Milan Crha 2018-06-08 13:19:16 UTC
For me too, in gdm screen, Fedora 28 virtual machine with:
gdm-3.28.1-1.fc28.x86_64
gnome-shell-3.28.2-1.fc28.x86_64
mesa-dri-drivers-18.0.2-1.fc28.x86_64

and also rawhide virtual machine with:
gdm-3.28.1-1.fc29.x86_64
gnome-shell-3.29.1-1.fc29.x86_64
mesa-dri-drivers-18.0.1-1.fc29.x86_64

I'll update rawhide to more recent versions and report back whether anything changed.

Comment 6 Milan Crha 2018-06-08 14:45:52 UTC
The same with:
gdm-3.28.2-1.fc29.x86_64
gnome-shell-3.29.2-1.fc29.x86_64
mesa-dri-drivers-18.1.1-2.fc29.x86_64
mutter-3.29.2-2.fc29.x86_64

Comment 7 Jan Kurik 2018-08-14 10:12:12 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.

Comment 8 Ben Cotton 2019-10-31 20:53:12 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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 9 Ben Cotton 2019-11-27 19:02:09 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.


Note You need to log in before you can comment on or make changes to this bug.