Summary: | [kwin_wayland] 100% cpu usage after user switching | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | c56w1t63 |
Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | buddha, c56w1t63, nate, notmart, smirky |
Priority: | NOR | ||
Version First Reported In: | 5.24.4 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | gdb backtrace |
Description
c56w1t63
2022-04-15 12:14:44 UTC
can you on the active session do gdb attach (the pid of the *other* running kwin, not the one which is rendering on the screen at the moment) at that point you can do ctrl+c and then bt to obtain a backtrace to see where it was at that moment *** This bug has been marked as a duplicate of bug 452726 *** Created attachment 148244 [details]
gdb backtrace
sudo gdb -pid 3332 -batch -ex "set logging file kwin_wayland.gdb" -ex "set logging on" -ex "continue" -ex "thread apply all backtrace" -ex "quit"
Any ideas? Because I can't work with multi user logged in as the cpu and fan usage is really high then. |