Bug 352415

Summary:	Balloo File Indexer crashes
Product:	[Unmaintained] Baloo	Reporter:	Nicholas <vanoudt>
Component:	Baloo File Daemon	Assignee:	Vishesh Handa <me>
Status:	RESOLVED FIXED
Severity:	crash	Keywords:	drkonqi, investigated, triaged
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Nicholas 2015-09-08 01:15:18 UTC

Application: baloo_file (5.13.0)

Qt Version: 5.5.0
Operating System: Linux 4.1.6-200.fc22.x86_64 x86_64
Distribution: "Fedora release 22 (Twenty Two)"

-- Information about the crash:
- What I was doing when the application crashed:
Simply restarting baloo causes the crash (balooctl start), wait a few minutes and it crashes

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Bus error
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb64337c840 (LWP 6003))]

Thread 3 (Thread 0x7fb62d3ea700 (LWP 6009)):
#0  0x00007fb63f6a82fd in poll () at /lib64/libc.so.6
#1  0x00007fb63a3ae182 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x00007fb63a3afc77 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x00007fb62fdb3999 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x00007fb6404c854e in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#5  0x00007fb63f161555 in start_thread () at /lib64/libpthread.so.0
#6  0x00007fb63f6b3b9d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fb4e7df2700 (LWP 6021)):
[KCrash Handler]
#5  0x00007fb63f65027e in __memcpy_sse2_unaligned () at /lib64/libc.so.6
#6  0x00007fb640217bb8 in mdb_page_touch () at /lib64/liblmdb.so.0.0.0
#7  0x00007fb6402182f0 in mdb_page_search () at /lib64/liblmdb.so.0.0.0
#8  0x00007fb64021e1bb in mdb_txn_commit () at /lib64/liblmdb.so.0.0.0
#9  0x00007fb640daaa00 in Baloo::Transaction::commit() () at /lib64/libKF5BalooEngine.so.5
#10 0x000000000041db85 in Baloo::ModifiedFileIndexer::run() ()
#11 0x00007fb6404c5043 in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5
#12 0x00007fb6404c854e in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#13 0x00007fb63f161555 in start_thread () at /lib64/libpthread.so.0
#14 0x00007fb63f6b3b9d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fb64337c840 (LWP 6003)):
#0  0x00007fb63f6a82fd in poll () at /lib64/libc.so.6
#1  0x00007fb63e9cedbc in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#2  0x00007fb63e9ceecc in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#3  0x00007fb6406ffdab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#4  0x00007fb6406a6daa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#5  0x00007fb6406aee6c in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#6  0x0000000000413f00 in main ()

Reported using DrKonqi

Comment 1 Vishesh Handa 2015-09-08 21:15:18 UTC

Hi. Since this seems to be reproducible. Could you please run baloo under valgrind?

$ valgrind baloo_file

and attach the output?

Comment 2 Vishesh Handa 2015-09-23 12:50:16 UTC

Ping?

Comment 3 Andrew Crouthamel 2018-09-04 19:46:12 UTC

Hello! This project has been replaced with a newer system so I will be closing this bug. If you could please re-test on the latest Baloo. If the issue still present, please open a new bug under "frameworks-baloo". Thank you!

Comment 4 Andrew Crouthamel 2018-09-19 14:33:33 UTC

This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.