Application: baloo_file (5.52.0) Qt Version: 5.11.2 Frameworks Version: 5.52.0 Operating System: Linux 4.15.0-39-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - Custom settings of the application: because baloo isn't functional using the kde settings, I start baloo from .bashrc. My system is a KDE Neon (bionic) fresh install The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc526d36800 (LWP 1458))] Thread 3 (Thread 0x7fc51b3fa700 (LWP 2577)): [KCrash Handler] #6 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:484 #7 0x00007fc525d4ebc3 in memcpy (__len=625498976, __src=<optimized out>, __dest=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34 #8 Baloo::PostingCodec::decode (this=this@entry=0x7fc51b3f9a07, arr=...) at ./src/codecs/postingcodec.cpp:42 #9 0x00007fc525d403f4 in Baloo::PostingDB::get (this=this@entry=0x7fc51b3f9af0, term=...) at ./src/engine/postingdb.cpp:100 #10 0x00007fc525d4c350 in Baloo::WriteTransaction::commit (this=0x7f850c09a290) at ./src/engine/writetransaction.cpp:264 #11 0x00007fc525d45a92 in Baloo::Transaction::commit (this=this@entry=0x7fc51b3f9c50) at ./src/engine/transaction.cpp:269 #12 0x00005593c2840621 in Baloo::IndexCleaner::run (this=0x5593c3a7ee60) at ./src/file/indexcleaner.cpp:79 #13 0x00007fc5251e5002 in QThreadPoolThread::run (this=0x5593c38fda90) at thread/qthreadpool.cpp:101 #14 0x00007fc5251edadb in QThreadPrivate::start (arg=0x5593c38fda90) at thread/qthread_unix.cpp:367 #15 0x00007fc52255a6db in start_thread (arg=0x7fc51b3fa700) at pthread_create.c:463 #16 0x00007fc52474788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fc51bdfc700 (LWP 1469)): #0 0x00007fc52473abf9 in __GI___poll (fds=0x7fc514003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x00007fc520906539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fc52090664c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fc52541304b in QEventDispatcherGlib::processEvents (this=0x7fc514000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x00007fc5253b730a in QEventLoop::exec (this=this@entry=0x7fc51bdfbd70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x00007fc5251e2bba in QThread::exec (this=<optimized out>) at thread/qthread.cpp:525 #6 0x00007fc525f6be45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x00007fc5251edadb in QThreadPrivate::start (arg=0x7fc5261e3d60) at thread/qthread_unix.cpp:367 #8 0x00007fc52255a6db in start_thread (arg=0x7fc51bdfc700) at pthread_create.c:463 #9 0x00007fc52474788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fc526d36800 (LWP 1458)): #0 0x00007fc5247360b4 in __GI___libc_read (fd=3, buf=0x7ffd5bd62da0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x00007fc52094acd0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fc520906027 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fc5209064e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007fc52090664c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007fc52541302f in QEventDispatcherGlib::processEvents (this=0x5593c3818920, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #6 0x00007fc5253b730a in QEventLoop::exec (this=this@entry=0x7ffd5bd62fb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #7 0x00007fc5253c04d0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1336 #8 0x00005593c28308fc in main (argc=<optimized out>, argv=<optimized out>) at ./src/file/main.cpp:104 The reporter indicates this bug may be a duplicate of or related to bug 367480. Possible duplicates by query: bug 396323, bug 396218, bug 391803, bug 390363. Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 367480 ***