https://bugs.kde.org/show_bug.cgi?id=493142
--- Comment #19 from postix <[email protected]> --- Unless it's now fixed in 6.4.2 for your, I believe it would make sense to get some profiling with https://github.com/KDAB/hotspot?tab=readme-ov-file#using You would record the kwin_wayland process with perf, while it's consuming 100% cpu and study afterwards the flamegraph in hotspot, to see, where it consumes most cycles. Hopefully, this would give a good clue. -- You are receiving this mail because: You are watching all bug changes.
