Bug 99225 - Fedora 25: Wayland causes gnome-shell's CPU usage to increase, and spike when moving the cursor
Summary: Fedora 25: Wayland causes gnome-shell's CPU usage to increase, and spike when...
Status: RESOLVED INVALID
Alias: None
Product: Wayland
Classification: Unclassified
Component: wayland (show other bugs)
Version: 1.5.0
Hardware: Other All
: medium normal
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-29 18:46 UTC by Nate Graham
Modified: 2017-01-07 19:49 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Nate Graham 2016-12-29 18:46:40 UTC 
I'm running Fedora 25 + GNOME 3.22 + Wayland on a 2016 HP Spectre x360 (Kaby Lake).

With X, gnome-shell usually idles at 0-22% of one processor core and using the trackpad barely increases this, if at all.

With Wayland, gnome-shell usually idles at 0-8% of one processor core and when I use the trackpad, gnome-shell immediately spikes in CPU and memory usage. Screen recording attached.

Note: the screen recording exacerbates the problem to a huge extent; when I'm *not* recording, drawing circles with the trackpad spikes gnome-shell to about 30-40% of one processor core, and gnome-shell idles at 0-8%. When screen recording, these increase to not 250% and 50%, respectively. But still, 30-40% of one processor core seems very high for just moving the cursor around.

This seems to be a Wayland issue since it entirely disappears when logging into an X session. I'm happy to collect any required information.
Comment 1 Michael Catanzaro 2017-01-07 19:04:14 UTC 
Hi, this is the bug tracker for Wayland protocol issues. Nobody is going to fix your issue here. I recommend reporting this issue on GNOME Bugzilla against the gnome-shell component.
Comment 2 Nate Graham 2017-01-07 19:49:05 UTC 
Not being sure whose issue it was, I already did that: https://bugzilla.gnome.org/show_bug.cgi?id=775162

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.