[kwin] [Bug 499405] kwin_x11 100% cpu and display locked
https://bugs.kde.org/show_bug.cgi?id=499405 TraceyC changed: What|Removed |Added Keywords||X11-only --- Comment #9 from TraceyC --- Adding the x11-only keyword -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 499405] kwin_x11 100% cpu and display locked
https://bugs.kde.org/show_bug.cgi?id=499405 --- Comment #8 from [email protected] --- Created attachment 178616 --> https://bugs.kde.org/attachment.cgi?id=178616&action=edit screenshot of flickering firefox nightly window When this lock occurs, after killing the process; some firefox windows show random firefox windows flickering within one firefox window -- cycling through multiple "windows" at fairly high speed. This image is the best representation I've captured. A video would better show what i s happening. Then, just moving the mouse over this window causes the flickering to stop and restore the window to normal. This issue occurs several times a day. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 499405] kwin_x11 100% cpu and display locked
https://bugs.kde.org/show_bug.cgi?id=499405 --- Comment #7 from [email protected] --- I should note this issue only occurs when I grab the title bar of a window to move it either slightly, or to another monitor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 499405] kwin_x11 100% cpu and display locked
https://bugs.kde.org/show_bug.cgi?id=499405 --- Comment #6 from [email protected] --- Created attachment 177977 --> https://bugs.kde.org/attachment.cgi?id=177977&action=edit bt full again... looks like mostly the same bt full. Another thing I'm noticing: a window which is behind others (maybe 1/2" visible) appears to be flickering. Will try to capture more details on next lockup. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 499405] kwin_x11 100% cpu and display locked
https://bugs.kde.org/show_bug.cgi?id=499405 --- Comment #5 from [email protected] --- 3rd time in a few minutes... strace shows nothing. Open to other debugging options... gdb: (gdb) bt full #0 0x7f3045126b5f in QRect::operator&(QRect const&) const () at /lib64/libQt6Core.so.6 #1 0x7f3048265814 in KWin::Window::nextInteractiveMoveGeometry(QPointF const&) const () at /lib64/libkwin.so.6 #2 0x7f304826e681 in KWin::Window::updateInteractiveMoveResize(QPointF const&, QFlags) () at /lib64/libkwin.so.6 #3 0x7f30482bb1c1 in KWin::X11Window::motionNotifyEvent(unsigned int, int, int, int, int, int) () at /lib64/libkwin.so.6 #4 0x7f30482bbec9 in KWin::X11Window::windowEvent(xcb_generic_event_t*) () at /lib64/libkwin.so.6 #5 0x7f30481297fe in KWin::Application::dispatchEvent(xcb_generic_event_t*) () at /lib64/libkwin.so.6 #6 0x7f3044fb460f in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long long*) () at /lib64/libQt6Core.so.6 #7 0x7f303fae0f31 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () at /lib64/libQt6XcbQpa.so.6 #8 0x7f303fae2446 in QXcbConnection::processXcbEvents(QFlags) () at /lib64/libQt6XcbQpa.so.6 #9 0x7f303fb021b7 in xcbSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt6XcbQpa.so.6 #10 0x7f3043b03e21 in g_main_context_dispatch_unlocked () at /lib64/libglib-2.0.so.0 #11 0x7f3043b06040 in g_main_context_iterate_unlocked.isra () at /lib64/libglib-2.0.so.0 #12 0x7f3043b06840 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #13 0x7f30452a4b53 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt6Core.so.6 #14 0x7f3044fc8e72 in QEventLoop::exec(QFlags) () at /lib64/libQt6Core.so.6 #15 0x7f3044fc48ba in QCoreApplication::exec() () at /lib64/libQt6Core.so.6 #16 0x55f7cc6b8643 in main () -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 499405] kwin_x11 100% cpu and display locked
https://bugs.kde.org/show_bug.cgi?id=499405 --- Comment #4 from [email protected] --- Created attachment 177968 --> https://bugs.kde.org/attachment.cgi?id=177968&action=edit rpm -qa --last Again. This time, grabbed title bar of emacs window which was across middle/right screens boundary and barely moved it when the lockup occurred. Attaching output of recent "rpm -qa --last"; given the frequency of occurrence, guessing this started after 1/31/25 or 1/29/25 updates. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 499405] kwin_x11 100% cpu and display locked
https://bugs.kde.org/show_bug.cgi?id=499405 --- Comment #3 from [email protected] --- yet again. This time it occurred without moving a window. A python script was importing millions of records into postgres and likely writing status info to konsole. Moving windows may be coincidental to konsole output? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 499405] kwin_x11 100% cpu and display locked
https://bugs.kde.org/show_bug.cgi?id=499405 --- Comment #2 from [email protected] --- This time, I was moving a firefox window from right-most display to middle one. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 499405] kwin_x11 100% cpu and display locked
https://bugs.kde.org/show_bug.cgi?id=499405 --- Comment #1 from [email protected] --- Just experienced another lockup. This time, via tty3, issues sigkill to kwin_x11 which restarted it and restored my session with all apps still running. At least, there is an acceptable workaround... -- You are receiving this mail because: You are watching all bug changes.
