https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #21 from Dāvis <davis...@gmail.com> --- Created attachment 166630 --> https://bugs.kde.org/attachment.cgi?id=166630&action=edit kwin_wayland (In reply to Jonathan Lopes from comment #16) > [...] > If I had enough time, I could try to plug a debugger on kwin_wayland to find > what is causing this problem. However, I have basically zero experience with > C++ debugging (although I can figure out with basic directions), so even if > I find some time to do it, I don't even know where to start. It's described in https://community.kde.org/KWin/Debugging#TL;DR_for_bug_reporters But I think "continue" there is wrong, atleast that didn't work for me, but this worked fine $ sudo -E gdb -pid (pidof kwin_wayland) -batch -ex "thread apply all backtrace" See attachment, but here's main thread: Thread 1 (Thread 0x758d15893a00 (LWP 1067690) "kwin_wayland"): #0 0x0000758d1a719616 in __GI_ppoll (fds=fds@entry=0x63fa9f7f1d40, nfds=nfds@entry=10, timeout=<optimized out>, timeout@entry=0x7ffc058d01b0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:42 #1 0x0000758d1ae98deb in ppoll (__ss=<optimized out>, __timeout=<optimized out>, __nfds=<optimized out>, __fds=<optimized out>) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcore_unix.cpp:123 #2 qt_ppoll (timeout_ts=0x7ffc058d01b0, nfds=10, fds=0x63fa9f7f1d40) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcore_unix.cpp:126 #3 qt_ppoll (timeout_ts=0x7ffc058d01b0, nfds=10, fds=0x63fa9f7f1d40) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcore_unix.cpp:123 #4 qt_safe_poll (fds=0x63fa9f7f1d40, nfds=nfds@entry=10, timeout_ts=timeout_ts@entry=0x7ffc058d0260) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcore_unix.cpp:158 #5 0x0000758d1ae9f65a in QEventDispatcherUNIX::processEvents (this=<optimized out>, flags=..., flags@entry=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/tools/qarraydatapointer.h:113 #6 0x0000758d1b7b26e2 in QUnixEventDispatcherQPA::processEvents (this=<optimized out>, flags=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/platform/unix/qunixeventdispatcher.cpp:27 #7 0x0000758d1ad43d6e in QEventLoop::processEvents (flags=..., this=0x7ffc058d03b0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventloop.cpp:100 #8 QEventLoop::exec (this=0x7ffc058d03b0, flags=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventloop.cpp:182 #9 0x0000758d1ad3c2b8 in QCoreApplication::exec () at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qflags.h:74 #10 0x0000758d1bcf0f0a in QApplication::exec () at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:2574 #11 0x000063fa9c538dee in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kwin/kwin-6.0.1/src/main_wayland.cpp:609 Currently for me this looks like one of the biggest issues for Plasma 6, because my today's journal size (just last ~7 hours) since I updated is already ~20 GiB (might be other log spam bugs aswell). And compare that with last 5 days (not counting today) when it's 26 GiB. So basically now in single day I generate more logs than previously in a week... `kwin_wayland` generates this warning at a rate of ~17 messages/second. Right now I have over 500k such entries in my journal while using Plasma 6 just for a day... -- You are receiving this mail because: You are watching all bug changes.
