https://bugs.kde.org/show_bug.cgi?id=486214
--- Comment #6 from Bill <billy.nl...@slmail.me> --- (In reply to Zamundaaa from comment #5) > I don't see anything particularly weird in the flamegraph, most of the CPU > time is in compositing and processing Wayland events. There is a somewhat > odd QThreadPool thing in there taking up a not insignificant part of CPU > time, but it's not enough to cause this issue I've made few more observations since. The issue is not persistent and constant as it was when I reported it, that seem to have been the right moment where I caught it in full swing. laptop was asleep for few hours after reporting this bug and I didn't see the same CPU usage by kwin_wayland that day. It does reaper occasionality, especially where it does uses significant cpu time just sitting around idling for some reason? -- You are receiving this mail because: You are watching all bug changes.
