https://bugs.kde.org/show_bug.cgi?id=517893
--- Comment #8 from Oscar Fuentes <[email protected]> --- (In reply to Zamundaaa from comment #6) > > As for kwin_wayland using CPU, that's not the problem, but slowing-down the > > whole system disproportionally to the CPU usage of kwin_waylang + video > > player. I'm convinced that kwin_wayland is using lots of memory bus > > bandwidth. > Video playback inherently does use a lot of memory bandwidth. It's a lot of > data to move around. I just read your blog post on https://zamundaaa.github.io/wayland/2026/05/06/making-wl-shm-fast.html and I'm quite convinced that your change will solve the problems that motivated this bug report to a large extent. Thank you. For the record, setting WIN_FORCE_SW_CURSOR=1 as the workaround mentioned on the upstream report didn't solve the compositor freezes. Tried Hyprland with the same workloads. System performance is impacted but no freezes nor the GUI feels sluggish as with kwin_wayland. -- You are receiving this mail because: You are watching all bug changes.
