Bug 385186 - baloo_file crashed after being disabled and then stopped (in that order)
Summary: baloo_file crashed after being disabled and then stopped (in that order)
Status: RESOLVED DUPLICATE of bug 367480
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.18.0
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2017-09-29 01:19 UTC by Dmitry 'RCL' Rekman
Modified: 2018-10-12 23:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry 'RCL' Rekman 2017-09-29 01:19:07 UTC
Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-75-generic x86_64
Distribution: Ubuntu 16.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed: I disabled baloo through balooctl (first "disable", then "stop"). The crash appeared after "stop"

-- 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".
[KCrash Handler]
#6  __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:245
#7  0x00007f02b6c218da in memcpy (__len=149728712, __src=<optimized out>, __dest=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string3.h:53
#8  Baloo::PostingCodec::decode (this=this@entry=0x7ffcd5e417ff, arr=...) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/codecs/postingcodec.cpp:42
#9  0x00007f02b6c0d814 in Baloo::PostingDB::get (this=this@entry=0x7ffcd5e418e0, term=...) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/postingdb.cpp:100
#10 0x00007f02b6c1e3c6 in Baloo::WriteTransaction::commit (this=<optimized out>) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/writetransaction.cpp:277
#11 0x00007f02b6c16032 in Baloo::Transaction::commit (this=this@entry=0x7ffcd5e41980) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/transaction.cpp:262
#12 0x000000000042a02b in Baloo::MetadataMover::moveFileMetadata (this=0x112daf0, from=..., to=...) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/metadatamover.cpp:58
#13 0x00007f02b6746baf in QtPrivate::QSlotObjectBase::call (a=0x7ffcd5e41ae0, r=0x7ffcd5e421a0, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#14 QMetaObject::activate (sender=sender@entry=0x112da60, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffcd5e41ae0) at kernel/qobject.cpp:3698
#15 0x00007f02b6747537 in QMetaObject::activate (sender=sender@entry=0x112da60, m=m@entry=0x644cc0 <KInotify::staticMetaObject>, local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffcd5e41ae0) at kernel/qobject.cpp:3578
#16 0x000000000042aaba in KInotify::moved (this=this@entry=0x112da60, _t1=..., _t2=...) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/obj-x86_64-linux-gnu/src/file/moc_kinotify.cpp:330
#17 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
#18 0x00007f02b6746baf in QtPrivate::QSlotObjectBase::call (a=0x7ffcd5e41d70, r=0x112da60, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#19 QMetaObject::activate (sender=sender@entry=0x118a300, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcd5e41d70) at kernel/qobject.cpp:3698
#20 0x00007f02b6747537 in QMetaObject::activate (sender=sender@entry=0x118a300, m=m@entry=0x7f02b6961780 <QSocketNotifier::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcd5e41d70) at kernel/qobject.cpp:3578
#21 0x00007f02b67c624e in QSocketNotifier::activated (this=this@entry=0x118a300, _t1=13) at .moc/moc_qsocketnotifier.cpp:134
#22 0x00007f02b67531cb in QSocketNotifier::event (this=0x118a300, e=<optimized out>) at kernel/qsocketnotifier.cpp:260
#23 0x00007f02b671836c in QCoreApplication::notify (event=0x7ffcd5e41e30, receiver=0x118a300, this=0x7ffcd5e42100) at kernel/qcoreapplication.cpp:1038
#24 QCoreApplication::notifyInternal (this=0x7ffcd5e42100, receiver=0x118a300, event=event@entry=0x7ffcd5e41e30) at kernel/qcoreapplication.cpp:965
#25 0x00007f02b676ec95 in QCoreApplication::sendEvent (event=0x7ffcd5e41e30, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224
#26 socketNotifierSourceDispatch (source=0x10ece60) at kernel/qeventdispatcher_glib.cpp:101
#27 0x00007f02b2d09197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007f02b2d093f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007f02b2d0949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x00007f02b676e7cf in QEventDispatcherGlib::processEvents (this=0x10ed240, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#31 0x00007f02b6715b4a in QEventLoop::exec (this=this@entry=0x7ffcd5e42040, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#32 0x00007f02b671dbec in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229
#33 0x000000000041698c in main (argc=1, argv=<optimized out>) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/main.cpp:88

Possible duplicates by query: bug 355219.

Reported using DrKonqi
Comment 1 Nate Graham 2018-10-12 23:06:15 UTC

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