https://bugs.kde.org/show_bug.cgi?id=456304
hexchain <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from hexchain <[email protected]> --- (In reply to David Edmundson from comment #2) > Does it also happen just going to an empty TTY. > Yes, it does. > The perf trace doesn't show anything special other than timers firing and us > idling, but we're probably doing that constantly with zero interval timers. > > Can you shove a debug in: > > ``` > QObject::connect(&compositeTimer, &QTimer::timeout, q, [this]() { > dispatch(); > }); > > ``` > > in renderloop.cpp and confirm if that's going crazy It doesn't seem to be this timer. I've put a qCWarning there every 100 times the timer gets fired, and when kwin_wayland was inactive and used 100% CPU, it wasn't producing any logs. -- You are receiving this mail because: You are watching all bug changes.
