Created attachment 123174 [details] Picture of the issue SUMMARY Since I upgraded to Qt 5.14 beta1, I have kwin_wayland using 25% of my CPU and artifacts while rendering the mouse cursor (see attached picture). STEPS TO REPRODUCE 1. Start plasma wayland session OBSERVED RESULT Mouse cursor artifacts and kwin_wayland process using 25% of available CPU. SOFTWARE/OS VERSIONS Linux/KDE Plasma: archlinux KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.63 Qt Version: 5.14 beta1 ADDITIONAL INFORMATION The issue stops happening: - if the mouse cursor is hovering the window title bar - if the mouse is hovering an xwayland window - if the screen is locked
Forgot to say this happens on a laptop with Intel graphics.
It seems flatpak Qt apps are also not affected.
related to bug 412760
*** Bug 412760 has been marked as a duplicate of this bug. ***
Anything suspicious in the output of an affected application with WAYLAND_DEBUG=1?
(In reply to Fabian Vogt from comment #5) > Anything suspicious in the output of an affected application with > WAYLAND_DEBUG=1? Yes, thanks for the hint: $ WAYLAND_DEBUG=1 dolphin ... [1647729.535] wl_callback@44.done(1578247) [1647729.547] -> wl_surface@43.set_buffer_scale(1) [1647729.557] -> wl_surface@43.attach(wl_buffer@42, 0, 0) [1647729.577] -> wl_surface@43.damage(0, 0, 32, 32) [1647729.605] -> wl_surface@43.frame(new id wl_callback@44) [1647729.619] -> wl_surface@43.commit() [1647729.742] wl_display@1.delete_id(44) [1647729.764] wl_callback@44.done(1578247) [1647729.777] -> wl_surface@43.set_buffer_scale(1) [1647729.786] -> wl_surface@43.attach(wl_buffer@42, 0, 0) [1647729.809] -> wl_surface@43.damage(0, 0, 32, 32) [1647729.833] -> wl_surface@43.frame(new id wl_callback@44) [1647729.848] -> wl_surface@43.commit() [1647729.965] wl_display@1.delete_id(44) [1647729.987] wl_callback@44.done(1578247) [1647730.000] -> wl_surface@43.set_buffer_scale(1) [1647730.009] -> wl_surface@43.attach(wl_buffer@42, 0, 0) [1647730.025] -> wl_surface@43.damage(0, 0, 32, 32) [1647730.048] -> wl_surface@43.frame(new id wl_callback@44) [1647730.062] -> wl_surface@43.commit() [1647730.184] wl_display@1.delete_id(44) [1647730.207] wl_callback@44.done(1578247) [1647730.220] -> wl_surface@43.set_buffer_scale(1) [1647730.229] -> wl_surface@43.attach(wl_buffer@42, 0, 0) [1647730.245] -> wl_surface@43.damage(0, 0, 32, 32) [1647730.270] -> wl_surface@43.frame(new id wl_callback@44) [1647730.282] -> wl_surface@43.commit() [1647730.392] wl_display@1.delete_id(44) [1647730.409] wl_callback@44.done(1578248) [1647730.421] -> wl_surface@43.set_buffer_scale(1) [1647730.433] -> wl_surface@43.attach(wl_buffer@42, 0, 0) [1647730.456] -> wl_surface@43.damage(0, 0, 32, 32) [1647730.483] -> wl_surface@43.frame(new id wl_callback@44) [1647730.504] -> wl_surface@43.commit() ... and so on. These functions are repeated in a loop while reproducing the issue.
Also here, exactly as above.
(In reply to Elvis Angelaccio from comment #2) > It seems flatpak Qt apps are also not affected. Possibly because the org.kde.Platform 5.13 runtime ships Qt 5.13.x
This problem persists after update to Qt 5.14 RC1. Operating System: Arch Linux KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.14.0 RC1
Fixed. https://code.qt.io/cgit/qt/qtwayland.git/commit/?h=5.14&id=36974955d13578071387695adb13a47be33e4d32
(In reply to David Edmundson from comment #10) > Fixed. > > https://code.qt.io/cgit/qt/qtwayland.git/commit/?h=5. > 14&id=36974955d13578071387695adb13a47be33e4d32 does Qt 5.14 include the fix? This problem persists after upgrade to Qt 5.14 on Arch Linux.
(In reply to Patrick Silva from comment #11) > (In reply to David Edmundson from comment #10) > > Fixed. > > > > https://code.qt.io/cgit/qt/qtwayland.git/commit/?h=5. > > 14&id=36974955d13578071387695adb13a47be33e4d32 > > does Qt 5.14 include the fix? > This problem persists after upgrade to Qt 5.14 on Arch Linux. The package from the testing repo includes the fix. I confirm that it fixes the issue.
yes, yesterday I installed qt5-wayland 5.14.0-2 package including the fix. \o/
This issue is still/again present.
>This issue is still/again present. As in the issue of generic high CPU or the specific issue of mouse cursor frames going at infinite fps?
(In reply to David Edmundson from comment #15) > >This issue is still/again present. > > As in the issue of generic high CPU or the specific issue of mouse cursor > frames going at infinite fps? Mouse cursor shadow has a breathing effect like it was described in the duplicate. I don't know about high CPU usage but my wayland session does run at 30fps or less (https://bugs.kde.org/show_bug.cgi?id=424398).
Can confirm relatively high CPU usage (showing 6% instead of nothing in systemmonitor. Also framerate breaks down from 120 frames to under 100 with sometimes even under 50 fps which is clearly visible mostly when using the virtual desktop overview with 4 virtual desktops showing side by side.
Looks like a memory leak to me. The process gradually uses more CPU and more and more memory on my system. So 120 fps at the beginning of a session and the more RAM it uses the slower the framerate gets.
It's been almost a year and no new similar bug reports, so it seems like the issue is gone. If you're still able to reproduce the bug, please reopen this bug report.