[kwin] [Bug 456304] kwin_wayland takes up 100% CPU after switching to another user
https://bugs.kde.org/show_bug.cgi?id=456304 kt47uo5u...@protonmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||kt47uo5u...@protonmail.com --- Comment #4 from kt47uo5u...@protonmail.com --- *** This bug has been marked as a duplicate of bug 452726 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456304] kwin_wayland takes up 100% CPU after switching to another user
https://bugs.kde.org/show_bug.cgi?id=456304
hexchain changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO |---
--- Comment #3 from hexchain ---
(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.
[kwin] [Bug 456304] kwin_wayland takes up 100% CPU after switching to another user
https://bugs.kde.org/show_bug.cgi?id=456304
David Edmundson changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
CC||k...@davidedmundson.co.uk
Status|REPORTED|NEEDSINFO
--- Comment #2 from David Edmundson ---
Does it also happen just going to an empty TTY.
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
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 456304] kwin_wayland takes up 100% CPU after switching to another user
https://bugs.kde.org/show_bug.cgi?id=456304 hexchain changed: What|Removed |Added Attachment #150379|0 |1 is obsolete|| --- Comment #1 from hexchain --- Created attachment 150389 --> https://bugs.kde.org/attachment.cgi?id=150389&action=edit perf record -g -p PID / perf report --stdio (with more debug info) -- You are receiving this mail because: You are watching all bug changes.
