[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 Christoph Feck changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #20 from Christoph Feck --- Thanks for the update; closing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 --- Comment #19 from José Pekkarinen --- I'm already far from the versions this happened to me too, so not reproducing anymore, it can be closed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 --- Comment #18 from tro...@free.fr --- It stopped happening here too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 --- Comment #17 from Mustafa Muhammad --- (In reply to Alexander Mentyu from comment #16) > Is this issue still reproducible? I don't think so, at least not for me, I don't mind closing it, it's your call. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #16 from Alexander Mentyu --- Is this issue still reproducible? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 --- Comment #15 from Mustafa Muhammad--- (In reply to Martin Flöser from comment #14) > What I need is to know where the problem happens. For that I ideally get a > backtrace with debug symbols. Without that all is just guessing > unfortunately. I'll try to provide another backtrace with debug symbols (I think I already provided one), but the session is very unstable these days (crash when I traverse the menu), so maybe later. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 --- Comment #14 from Martin Flöser--- What I need is to know where the problem happens. For that I ideally get a backtrace with debug symbols. Without that all is just guessing unfortunately. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 José Pekkarinenchanged: What|Removed |Added CC||koali...@gmail.com --- Comment #13 from José Pekkarinen --- Same here with gentoo, unmasking plasma 5.9.5. Is there any interesting info I could share to ease the debugging? I'm afraid debugging symbols won't be there either. Thanks! José. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 Rex Dieterchanged: What|Removed |Added CC||rdie...@math.unl.edu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 Andrei Amurariteichanged: What|Removed |Added Ever confirmed|0 |1 CC||sird...@bydeiu.net Status|UNCONFIRMED |CONFIRMED --- Comment #12 from Andrei Amuraritei --- Hi, I'm seeing this also on Fedora 25 x86_64 with Plasma 5.9.4, choosing the wayland sesssion and logging in or starting a nested wayland session shows kwin_wayland using 100% cpu. This on a optimus Acer laptop (intel 530 skylake and nouveau for nvidia gtx950m). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 e.ekme...@gmail.com changed: What|Removed |Added CC||e.ekme...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 tro...@free.fr changed: What|Removed |Added CC||tro...@free.fr --- Comment #11 from tro...@free.fr --- Getting this too. On Arch Linux, Plasma 5.9.3, Kwin_wayland suddenly took 100% of one core of my CPU after a few hours of use. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 --- Comment #10 from Martin Gräßlin--- > It is the same process, still running until now if you want something, > maybe > different timing can cause different gdb output :) sure, sure. But if we have 100 % cpu usage cases, it's quite often, that gdb ends in the same area. Which is why I was interested in gdb in the first place. I just hoped, that it ends up always in the same spot - that would make investigating easier. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 --- Comment #9 from Mustafa Muhammad--- It is the same process, still running until now if you want something, maybe different timing can cause different gdb output :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 --- Comment #8 from Martin Gräßlin--- It hit a completely different place. This time we don't have Wayland server event loop in the backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 --- Comment #7 from Mustafa Muhammad--- Created attachment 103912 --> https://bugs.kde.org/attachment.cgi?id=103912=edit trace with debug packages installed I installed all debug packages I could find in the file and generated a new trace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 --- Comment #6 from Martin Gräßlin--- Difficult to say. We have many "No symbol table info available." which means we don't see the actual code line. What we see is it is dispatching the Wayland server event loop. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 --- Comment #5 from Mustafa Muhammad--- Created attachment 103904 --> https://bugs.kde.org/attachment.cgi?id=103904=edit kwin_wayland trace -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 --- Comment #4 from Mustafa Muhammad--- It happens sometimes, I didn't use gdb before, I used: gdb -p `pidof kwin_wayland` -ex bt -ex 'thread apply all bt full' -ex detach -ex quit &> kwin_wayland_trace to create the attached file, hope it helps, please let me know if there is anything else I can provide -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 --- Comment #3 from Martin Gräßlin--- What might be better is a gdb backtrace of the stuck process. In general it works in neon wayland dev unstable, I'm just writing in such a session. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 --- Comment #2 from Mustafa Muhammad--- Created attachment 103806 --> https://bugs.kde.org/attachment.cgi?id=103806=edit strace -c -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 --- Comment #1 from Mustafa Muhammad--- Created attachment 103805 --> https://bugs.kde.org/attachment.cgi?id=103805=edit strace -- You are receiving this mail because: You are watching all bug changes.