https://bugs.kde.org/show_bug.cgi?id=428416
--- Comment #2 from Carl Schwan <[email protected]> --- Using balooctl to disable the baloo doesn't stop the process, this makes me think that there is an infinite loop. Attaching gdb to the running process gives me: #0 0x00007f3f921d3527 in __memmove_avx_unaligned_erms () from /lib64/libc.so.6 #1 0x00007f3f92b246ea in memmove (__len=<optimized out>, __src=<optimized out>, __dest=<optimized out>, __dest=<optimized out>, __src=<optimized out>, __len=<optimized out>) at /usr/include/qt5/QtCore/qvector.h:838 #2 QVector<Baloo::PositionInfo>::insert (before=..., before=..., n=1, t=..., this=0x7f3f8d6818e8) at /usr/include/qt5/QtCore/qvector.h:863 #3 QVector<Baloo::PositionInfo>::insert (x=..., before=..., this=0x7f3f8d6818e8) at /usr/include/qt5/QtCore/qvector.h:235 #4 Baloo::sortedIdInsert<QVector<Baloo::PositionInfo>, Baloo::PositionInfo> (id=..., vec=...) at /usr/src/debug/baloo5-5.75.0-1.1.x86_64/src/engine/idutils.h:90 #5 Baloo::WriteTransaction::commit (this=<optimized out>) at /usr/src/debug/baloo5-5.75.0-1.1.x86_64/src/engine/writetransaction.cpp:299 #6 0x00007f3f92b1883b in Baloo::Transaction::commit (this=this@entry=0x7f3f8d681aa0) at /usr/src/debug/baloo5-5.75.0-1.1.x86_64/src/engine/transaction.cpp:275 #7 0x000055da09973ad3 in Baloo::UnindexedFileIndexer::run (this=0x55da0bba8480) at /usr/src/debug/baloo5-5.75.0-1.1.x86_64/src/file/unindexedfileindexer.cpp:61 #8 0x00007f3f926356f2 in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x00007f3f92631911 in ?? () from /usr/lib64/libQt5Core.so.5 #10 0x00007f3f9158deb1 in start_thread () from /lib64/libpthread.so.0 #11 0x00007f3f9216dccf in clone () from /lib64/libc.so.6 and typing next: Single stepping until exit from function __memmove_avx_unaligned_erms, which has no line number information. Another helpful information is that I actually have two baloo_file process. The second one give me this backtrace when attaching gdb: #0 0x00007f3f91594082 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f3f9263792b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib64/libQt5Core.so.5 #2 0x00007f3f92634277 in QThreadPoolPrivate::waitForDone(QDeadlineTimer const&) () from /usr/lib64/libQt5Core.so.5 #3 0x00007f3f92634697 in QThreadPoolPrivate::waitForDone(int) () from /usr/lib64/libQt5Core.so.5 #4 0x00007f3f9263472c in QThreadPool::~QThreadPool() () from /usr/lib64/libQt5Core.so.5 #5 0x000055da0996ac8d in ?? () #6 0x000055da0996acd8 in ?? () #7 0x000055da09961210 in ?? () #8 0x00007f3f92095e0a in __libc_start_main () from /lib64/libc.so.6 #9 0x000055da099616aa in ?? () Unfortunally I'm using my distro package and they are optimized so I can't inspect the state of the different variables. -- You are receiving this mail because: You are watching all bug changes.
