GNOME Bugzilla – Bug 783017
GNOME Shell lags and slows down after a while under Wayland
Last modified: 2021-07-05 13:48:59 UTC
I use GNOME Shell 3.22 on Fedora 25 for a while now (since the beta was released), 2 months ago it started to lag and slow down after some time (maybe a day or two of usage). The issues appear clearly when you move your mouse cursor over a tooltip in Firefox (XWayland) or click on a menu in LibreOffice 5.2 (GTK3 Wayland). Video Players starts to suffer when switching to full screen mode (where the GNOME shell top bar should hide), it may take forever to switch and the whole Shell become unresponsive for over a minute. Using double-click to full screen is always better than using the keyboard hot-key "F" to switch, because "F" sometimes switches to full-screen then switches back at the same instant. Every extra hour in this state renders the system slower and more unresponsive until it completely crashes at the end (maybe like 5 days in a row). I was able to guess-pin-point the issue on mutter as I downgraded to mutter 3.22.1 (the first version came with Fedora 25) and all these problems were gone, but I couldn't like "bisect" the versions to exactly the version that started to cause this. Also, the journal logs are spammed with a lot of GNOME Shell messages mentioning "Mutter" errors (especially, when I switch between work-spaces). I still can't log the issue accurately, so I need your help to know how to debug the issue and generate a useful log for the developers to work on this issue.
Can you confirm that the issue is introduced between 3.22.1 and 3.22.2? What are the "Mutter" errors in the journal logs?
(In reply to Jonas Ådahl from comment #1) > Can you confirm that the issue is introduced between 3.22.1 and 3.22.2? > > What are the "Mutter" errors in the journal logs? I don't know, I know that I tried 3.22.1 and it worked flawlessly for days (as it used to be) .. I have to downgrade again to this specific (3.22.2) version. the testing takes days to start lagging and slowing down. I've installed this build from Koji: https://koji.fedoraproject.org/koji/buildinfo?buildID=823521 because I think the problem started appearing around March and April 2017.
(In reply to Jonas Ådahl from comment #1) > Can you confirm that the issue is introduced between 3.22.1 and 3.22.2? > > What are the "Mutter" errors in the journal logs? You asked me about the errors in the logs, I think they've disappeared for a while but I'm seeing them again after I downgraded to mutter 3.22.2: May 28 14:16:31 anass-galago gnome-shell[1864]: clutter_layout_manager_get_child_meta: assertion 'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed May 28 14:16:31 anass-galago gnome-shell[1864]: g_object_set: assertion 'G_IS_OBJECT (object)' failed May 28 14:16:31 anass-galago gnome-shell[1864]: g_object_set: assertion 'G_IS_OBJECT (object)' failed
Looks like this bug is duplicate of various bugs already reported here, for example: https://bugzilla.gnome.org/show_bug.cgi?id=745032 This bug really covers most of the issues I have with GNOME under Wayland (Mouse lags, frame-drops, keyboard input stutters, memory leaks after a while) but I didn't find it before I file this report. Also, it wasn't that bad before March 2017 as far as I remember. I'm now using mutter 3.22.2-3 for the second day and I don't encounter the worst performance like I did with the following versions of mutter. The issue still is apparent with GTK3 apps (especially in menus) like LibreOffice 5.2 where the mouse lags and the menu doesn't appear right away when you click on it. NOTE: I'm using GNOME on Wayland since F24.
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/mutter/-/issues/ Thank you for your understanding and your help.