Bug 368519 - Baloo File Indexing Daemon crashes consistently after boot
Summary: Baloo File Indexing Daemon crashes consistently after boot
Status: RESOLVED DUPLICATE of bug 360946
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Engine (show other bugs)
Version: 5.18.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-09-09 19:27 UTC by Braden Anderson
Modified: 2017-10-27 17:21 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Braden Anderson 2016-09-09 19:27:08 UTC
Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-31-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
Baloo crashes after booting the system, logging in, and performing almost any activity, such as opening a KDE Wallet, opening the file explorer, or launching my development Rails server.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__lll_robust_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevelrobustlock.S:85
[Current thread is 1 (Thread 0x7f1e5a414900 (LWP 5028))]

Thread 2 (Thread 0x7f1d19e00700 (LWP 7158)):
[KCrash Handler]
#6  0x00007f1e64413418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#7  0x00007f1e6441501a in __GI_abort () at abort.c:89
#8  0x00007f1e62a14002 in mdb_assert_fail (env=0x118ce60, expr_txt=expr_txt@entry=0x7f1e62a15a5f "rc == 0", func=func@entry=0x7f1e62a16398 <__func__.7098> "mdb_page_dirty", line=line@entry=2065, file=0x7f1e62a15a40 "mdb.c") at mdb.c:1481
#9  0x00007f1e62a096a5 in mdb_page_dirty (txn=0x1204c90, mp=<optimized out>) at mdb.c:2065
#10 0x00007f1e62a0a863 in mdb_page_alloc (num=num@entry=1, mp=mp@entry=0x7f1d19dff2b0, mc=<optimized out>) at mdb.c:2246
#11 0x00007f1e62a0c754 in mdb_page_new (mc=mc@entry=0x7f1d19dff940, flags=flags@entry=1, num=num@entry=1, mp=mp@entry=0x7f1d19dff378) at mdb.c:6928
#12 0x00007f1e62a0d28a in mdb_page_split (mc=mc@entry=0x7f1d19dff940, newkey=newkey@entry=0x7f1d19dff890, newdata=0x7f1d19dff8a0, newpgno=newpgno@entry=18446744073709551615, nflags=nflags@entry=65536) at mdb.c:8359
#13 0x00007f1e62a0fc70 in mdb_cursor_put (mc=0x7f1d19dff940, key=0x7f1d19dff890, data=0x7f1d19dff8a0, flags=<optimized out>) at mdb.c:6682
#14 0x00007f1e62a1156e in mdb_freelist_save (txn=0x1204c90) at mdb.c:3137
#15 mdb_txn_commit (txn=0x1204c90) at mdb.c:3555
#16 0x00007f1e655b6070 in Baloo::Transaction::commit (this=this@entry=0x7f1d19dffb90) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/transaction.cpp:266
#17 0x000000000041c8e0 in Baloo::NewFileIndexer::run (this=0x1931c70) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/newfileindexer.cpp:75
#18 0x00007f1e64ed4343 in QThreadPoolThread::run (this=0x15e6190) at thread/qthreadpool.cpp:93
#19 0x00007f1e64ed784e in QThreadPrivate::start (arg=0x15e6190) at thread/qthread_unix.cpp:331
#20 0x00007f1e641c86fa in start_thread (arg=0x7f1d19e00700) at pthread_create.c:333
#21 0x00007f1e644e4b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f1e5a414900 (LWP 5028)):
#0  __lll_robust_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevelrobustlock.S:85
#1  0x00007f1e641caa28 in __pthread_mutex_lock_full (mutex=0x7f1e665d2040) at ../nptl/pthread_mutex_lock.c:256
#2  0x00007f1e62a08c32 in mdb_txn_renew0 (txn=txn@entry=0x1204c90) at mdb.c:2692
#3  0x00007f1e62a09f14 in mdb_txn_begin (env=0x118ce60, parent=parent@entry=0x0, flags=flags@entry=0, ret=ret@entry=0x7ffec8241498) at mdb.c:2850
#4  0x00007f1e655b599b in Baloo::Transaction::Transaction (this=0x7ffec8241490, db=..., type=Baloo::Transaction::ReadWrite) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/transaction.cpp:53
#5  0x000000000042a004 in Baloo::MetadataMover::moveFileMetadata (this=0x113cff0, from=..., to=...) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/metadatamover.cpp:49
#6  0x00007f1e650e6e4f in QtPrivate::QSlotObjectBase::call (a=0x7ffec82415f0, r=0x7ffec8241cb0, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#7  QMetaObject::activate (sender=sender@entry=0x1113c00, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffec82415f0) at kernel/qobject.cpp:3698
#8  0x00007f1e650e77d7 in QMetaObject::activate (sender=sender@entry=0x1113c00, m=m@entry=0x644cc0 <KInotify::staticMetaObject>, local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffec82415f0) at kernel/qobject.cpp:3578
#9  0x000000000042aaba in KInotify::moved (this=this@entry=0x1113c00, _t1=..., _t2=...) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/obj-x86_64-linux-gnu/src/file/moc_kinotify.cpp:330
#10 0x000000000042cbff in KInotify::slotEvent (this=<optimized out>, socket=<optimized out>) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/kinotify.cpp:421
#11 0x00007f1e650e6e4f in QtPrivate::QSlotObjectBase::call (a=0x7ffec8241880, r=0x1113c00, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#12 QMetaObject::activate (sender=sender@entry=0x117ad30, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffec8241880) at kernel/qobject.cpp:3698
#13 0x00007f1e650e77d7 in QMetaObject::activate (sender=sender@entry=0x117ad30, m=m@entry=0x7f1e65301780 <QSocketNotifier::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffec8241880) at kernel/qobject.cpp:3578
#14 0x00007f1e6516651e in QSocketNotifier::activated (this=this@entry=0x117ad30, _t1=13) at .moc/moc_qsocketnotifier.cpp:134
#15 0x00007f1e650f347b in QSocketNotifier::event (this=0x117ad30, e=<optimized out>) at kernel/qsocketnotifier.cpp:260
#16 0x00007f1e650b860c in QCoreApplication::notify (event=0x7ffec8241940, receiver=0x117ad30, this=0x7ffec8241c10) at kernel/qcoreapplication.cpp:1038
#17 QCoreApplication::notifyInternal (this=0x7ffec8241c10, receiver=0x117ad30, event=event@entry=0x7ffec8241940) at kernel/qcoreapplication.cpp:965
#18 0x00007f1e6510ef45 in QCoreApplication::sendEvent (event=0x7ffec8241940, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224
#19 socketNotifierSourceDispatch (source=0x1100dd0) at kernel/qeventdispatcher_glib.cpp:101
#20 0x00007f1e616a91a7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f1e616a9400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f1e616a94ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f1e6510ea7f in QEventDispatcherGlib::processEvents (this=0x11018d0, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#24 0x00007f1e650b5dea in QEventLoop::exec (this=this@entry=0x7ffec8241b50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#25 0x00007f1e650bde8c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229
#26 0x000000000041698c in main (argc=1, argv=<optimized out>) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/main.cpp:88

Reported using DrKonqi
Comment 1 Christoph Cullmann 2016-09-11 17:11:35 UTC
How large is your

./local/share/baloo/index

file?
Comment 2 Braden Anderson 2016-09-11 22:16:25 UTC
(In reply to Christoph Cullmann from comment #1)
> How large is your
> 
> ./local/share/baloo/index
> 
> file?

My ~/.local/share/baloo/index is 1.1 GB.
Comment 3 Christoph Cullmann 2016-09-12 09:07:06 UTC
Hmm,
if you delete that file, does it still crash? (that kills your index, but if it crashs, thats not that important)
Comment 4 Christoph Cullmann 2016-09-12 09:07:51 UTC
(btw., before you do that, what does

balooctl status

say?)
Comment 5 Braden Anderson 2016-09-12 17:42:28 UTC
$ balooctl status
Baloo File Indexer is not running
Indexed 36695 / 36695 files
Current size of index is 1.10 GiB

I've deleted the index and will let you know if it crashes next time I reboot.
Comment 6 Nate Graham 2017-10-27 17:21:22 UTC

*** This bug has been marked as a duplicate of bug 360946 ***