On Thu, Sep 5, 2024 at 12:00 PM Peter Humphrey <pe...@prh.myzen.co.uk> wrote: > > On Thursday 5 September 2024 15:43:00 BST Iwrote: > > On Thursday 5 September 2024 13:47:29 BST I wrote: > > > ... Perhaps I should start recompiling things... > > > > After an emerge -e1 kwayland plasma-workspace and a reboot, kwin_wayland is > > down to 20-60% CPU and plasma_shell is barely visible in /top/. > > > > Much improved, but it still isn't right. > > It came back again, so I ran a complete -e, rebooted, recompiled the kernel > again and rebooted again. > > It's all back as it was - no CPU cycles left for anything else but wayland and > plasam-shell. > > How to debug this? > > -- > Regards, > Peter.
If you are running systemd then you can try systemd-cgtop which should identify what slice, if any, is using lots of CPU. If you were interested in exploring more deeply you might be able to create a control group that Wayland could run inside of to limit resources or possible identify what part of Wayland is getting out of control
