https://bugs.kde.org/show_bug.cgi?id=427471
--- Comment #3 from roa...@protonmail.com <roa...@protonmail.com> --- okay, so its using up anywhere from 18-24% overall CPU (2 threads entirely). here's the backtrace from gdb: > #0 0x00007ffff7dc537f in poll () at /usr/lib/libc.so.6 > #1 0x00007ffff3cdddef in () at /usr/lib/libglib-2.0.so.0 > #2 0x00007ffff3c856d1 in g_main_context_iteration () at > /usr/lib/libglib-2.0.so.0 > #3 0x00007ffff5d60681 in > QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () > at /usr/lib/libQt5Core.so.5 > #4 0x00007ffff5d0639c in > QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at > /usr/lib/libQt5Core.so.5 > #5 0x00007ffff5d0e834 in QCoreApplication::exec() () at > /usr/lib/libQt5Core.so.5 > #6 0x00007ffff7ee5f43 in kdemain () at /usr/lib/libkdeinit5_dolphin.so > #7 0x00007ffff7cf8b25 in __libc_start_main () at /usr/lib/libc.so.6 > #8 0x000055555555505e in _start () -- You are receiving this mail because: You are watching all bug changes.
