SUMMARY I forgot to close the window at the very end of the bug reporting procedure. After some time, I noticed the CPU fan spinning up because the drkonqi process was spinning and using 100% of one core. STEPS TO REPRODUCE 1. File a bug 2. When you see "Thank you for being part of KDE. You can now close this window." -- don't! Leave the window open 3. Check CPU usage with top SOFTWARE/OS VERSIONS KDE Plasma Version: 6.3.5 KDE Frameworks Version: 5.116.0 Qt Version: 6.9.0
I attached gdb to capture a stacktrace: #0 0x00007fffb895a3d7 in KQuickStyleItem::eventFilter(QObject*, QEvent*) () at /usr/lib64/qt6/qml/org/kde/qqc2desktopstyle/private/libqqc2desktopstyleplugin.so #1 0x00007ffff52f5c2a in QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*) () at /lib64/libQt6Core.so.6 #2 0x00007ffff683d7cb in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt6Widgets.so.6 #3 0x00007ffff52f5fa8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt6Core.so.6 #4 0x00007ffff52f9cd6 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt6Core.so.6 #5 0x00007ffff55ffd2f in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt6Core.so.6 #6 0x00007ffff4824040 in g_main_context_dispatch_unlocked.lto_priv () at /lib64/libglib-2.0.so.0 #7 0x00007ffff482d128 in g_main_context_iterate_unlocked.isra () at /lib64/libglib-2.0.so.0 #8 0x00007ffff482d2d3 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #9 0x00007ffff55ff56d in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt6Core.so.6 #10 0x00007ffff5303783 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt6Core.so.6 #11 0x00007ffff52ff229 in QCoreApplication::exec() () at /lib64/libQt6Core.so.6 #12 0x000055555556a50c in main () And also: #0 0x00007fffb895a3d7 in KQuickStyleItem::eventFilter(QObject*, QEvent*) () at /usr/lib64/qt6/qml/org/kde/qqc2desktopstyle/private/libqqc2desktopstyleplugin.so #1 0x00007ffff52f5c2a in QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*) () at /lib64/libQt6Core.so.6 #2 0x00007ffff683d7cb in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt6Widgets.so.6 #3 0x00007ffff52f5fa8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt6Core.so.6 #4 0x00007ffff52f9cd6 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt6Core.so.6 #5 0x00007ffff55ffd2f in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt6Core.so.6 #6 0x00007ffff4824040 in g_main_context_dispatch_unlocked.lto_priv () at /lib64/libglib-2.0.so.0 #7 0x00007ffff482d128 in g_main_context_iterate_unlocked.isra () at /lib64/libglib-2.0.so.0 #8 0x00007ffff482d2d3 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #9 0x00007ffff55ff56d in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt6Core.so.6 #10 0x00007ffff5303783 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt6Core.so.6 #11 0x00007ffff52ff229 in QCoreApplication::exec() () at /lib64/libQt6Core.so.6 #12 0x000055555556a50c in main ()
Hidden spinner consuming CPU resources, maybe? What application style are you using?
Updating the status, pending information from the reporter
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
(In reply to Nate Graham from comment #2) > Hidden spinner consuming CPU resources, maybe? Is there a way to test filing bugs without bothering anyone? Maybe a test component in bugzilla? > What application style are you using? Application Style is simply Breeze (dark).
Cannot reproduce on 6.4beta
Hi - I tried reproducing this in a Neon VM. After the Crash Report Sent screen showed up, drkonqi wasn't using a huge amount of CPU, but gdb was using a decent amount of CPU and had increasing memory usage - up until either it finally finished, or was stopped by the out-of-memory killer. Just to double-check, was it definitely the drkonqi process, and not gdb, that was using up those resources? And if you're able to try reproducing, I'm consistently able to reproduce this bug on an up-to-date system: https://bugs.kde.org/show_bug.cgi?id=498846 Thanks!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.