FS#53757 - [gnome-shell] Laggy animations and high CPU usage.

Attached to Project: Arch Linux
Opened by metaph (metaph) - Saturday, 22 April 2017, 20:30 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 04 May 2021, 12:49 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description: GNOME has become very laggy after upgrading to 3.24.1, animations aren't fluid and CPU usage is untypically high.

My GPU is GTX 970, running with proprietary NVIDIA drivers and default ARCH kernel (4.10.11).

Additional info:
GNOME 3.24.1


Steps to reproduce:
Upgrade to GNOME 3.24.1.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Tuesday, 04 May 2021, 12:49 GMT
Reason for closing:  Fixed
Additional comments about closing:  no response from opener; fixed upstream
Comment by Bunyi Production (bunyi) - Wednesday, 26 April 2017, 09:14 GMT
The same here on GTX 760
Comment by Felix Cobos (fcobos) - Wednesday, 26 April 2017, 14:11 GMT
Maybe  FS#53704  is the cause of this?
Comment by loqs (loqs) - Friday, 28 April 2017, 20:31 GMT
https://bbs.archlinux.org/viewtopic.php?id=225584 / https://bugzilla.gnome.org/show_bug.cgi?id=781835 ?
Comment by metaph (metaph) - Monday, 01 May 2017, 01:29 GMT
https://bugzilla.gnome.org/show_bug.cgi?id=781835 - This seems to be the case, reverting this commit: https://git.gnome.org/browse/mutter/commit/?id=383ba566bd7c2a76d0856015a66e47caedef06b6 fixes the issue completely.
Comment by Léo (Leeo97one) - Sunday, 07 May 2017, 09:53 GMT
So I guess this is not related to Arch Linux.
Comment by Hussam Al-Tayeb (hussam) - Monday, 06 November 2017, 21:22 GMT
I found a dirty workaround to this from Arch Linux wiki. export __GL_YIELD="USLEEP"
The high cpu in gnome-shell/mutter stopped.
There is a performance loss in games but it's not bad on a new pascal card.
Comment by mattia (nTia89) - Wednesday, 06 November 2019, 12:01 GMT
Issue has been fixed upstream (upstream bug has been closed).
Can we close this as well?

Loading...