Bug 403720 - Baloo crashes at KDE session start.
Summary: Baloo crashes at KDE session start.
Status: RESOLVED DUPLICATE of bug 357206
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.45.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: baloo-bugs-null
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2019-01-29 06:21 UTC by Kai T. Ohlhus
Modified: 2019-03-13 21:50 UTC (History)
2 users (show)

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


Attachments
New crash information added by DrKonqi (4.00 KB, text/plain)
2019-02-01 23:52 UTC, Wantoyo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kai T. Ohlhus 2019-01-29 06:21:54 UTC
Application: baloo_file (5.45.0)

Qt Version: 5.9.4
Frameworks Version: 5.45.0
Operating System: Linux 4.12.14-lp150.12.45-default x86_64
Distribution: "openSUSE Leap 15.0"

-- Information about the crash:
- What I was doing when the application crashed:

The crash happens immediately after I logged in to my KDE session.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe671559100 (LWP 2205))]

Thread 3 (Thread 0x7fe666179700 (LWP 3389)):
[KCrash Handler]
#6  0x00007fe66efde58c in __memmove_avx_unaligned_erms () from /lib64/libc.so.6
#7  0x00007fe670562a93 in memcpy (__len=2051, __src=<optimized out>, __dest=<optimized out>) at /usr/include/bits/string_fortified.h:34
#8  Baloo::PostingCodec::decode (this=this@entry=0x7fe666178997, arr=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/codecs/postingcodec.cpp:42
#9  0x00007fe670553f64 in Baloo::PostingDB::get (this=this@entry=0x7fe666178a80, term=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/postingdb.cpp:100
#10 0x00007fe670560180 in Baloo::WriteTransaction::commit (this=0x5602767038e0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/writetransaction.cpp:259
#11 0x00007fe6705594c2 in Baloo::Transaction::commit (this=this@entry=0x7fe666178b90) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/transaction.cpp:262
#12 0x0000560274ecd6cd in Baloo::NewFileIndexer::run (this=0x5602766cfa90) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/file/newfileindexer.cpp:75
#13 0x00007fe66f9c6372 in QThreadPoolThread::run (this=0x5602765d4980) at thread/qthreadpool.cpp:99
#14 0x00007fe66f9c90ce in QThreadPrivate::start (arg=0x5602765d4980) at thread/qthread_unix.cpp:368
#15 0x00007fe66dfd3559 in start_thread () from /lib64/libpthread.so.0
#16 0x00007fe66ef7c81f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fe666c7c700 (LWP 2209)):
#0  0x00007fe66ef7207b in poll () from /lib64/libc.so.6
#1  0x00007fe66b6591c9 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007fe66b6592dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007fe66fbecc0b in QEventDispatcherGlib::processEvents (this=0x7fe660000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x00007fe66fb9509a in QEventLoop::exec (this=this@entry=0x7fe666c7bca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x00007fe66f9c44da in QThread::exec (this=<optimized out>) at thread/qthread.cpp:515
#6  0x00007fe670e09985 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x00007fe66f9c90ce in QThreadPrivate::start (arg=0x7fe671079d60) at thread/qthread_unix.cpp:368
#8  0x00007fe66dfd3559 in start_thread () from /lib64/libpthread.so.0
#9  0x00007fe66ef7c81f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fe671559100 (LWP 2205)):
#0  0x00007fe66ef7207b in poll () from /lib64/libc.so.6
#1  0x00007fe66b6591c9 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007fe66b6592dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007fe66fbecbef in QEventDispatcherGlib::processEvents (this=0x560276578d60, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#4  0x00007fe66fb9509a in QEventLoop::exec (this=this@entry=0x7fff34679740, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x00007fe66fb9d9e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1289
#6  0x0000560274ec521c in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/file/main.cpp:104
[Inferior 1 (process 2205) detached]

The reporter indicates this bug may be a duplicate of or related to bug 403483.

Possible duplicates by query: bug 403483, bug 403310, bug 403282, bug 403205, bug 402787.

Reported using DrKonqi
Comment 1 Wantoyo 2019-02-01 23:52:04 UTC
Created attachment 117782 [details]
New crash information added by DrKonqi

baloo_file (5.54.0) using Qt 5.12.0

Every login always displays this crash

Operating System: openSUSE Tumbleweed 20190126
KDE Plasma Version: 5.14.5
Qt Version: 5.12.0
KDE Frameworks Version: 5.54.0
Kernel Version: 4.20.2-1-default
OS Type: 64-bit
Processors: 3 × AMD Athlon(tm) II X3 440 Processor
Memory: 7,8 GiB of RAM

-- Backtrace (Reduced):
#7  0x00007fbd004868cd in memcpy (__len=1, __src=0x7f7cec1ae520, __dest=<optimized out>) at /usr/include/bits/string_fortified.h:34
#8  Baloo::PostingCodec::decode (this=this@entry=0x7fbcf9e5b8c7, arr=...) at /usr/src/debug/baloo5-5.54.0-1.1.x86_64/src/codecs/postingcodec.cpp:42
#9  0x00007fbd00473ee9 in Baloo::PostingDB::get (this=this@entry=0x7fbcf9e5b9b0, term=...) at /usr/src/debug/baloo5-5.54.0-1.1.x86_64/src/engine/postingdb.cpp:100
#10 0x00007fbd0048413a in Baloo::WriteTransaction::commit (this=0x7f7cec003400) at /usr/src/debug/baloo5-5.54.0-1.1.x86_64/src/engine/writetransaction.cpp:275
#11 0x00007fbd0047a712 in Baloo::Transaction::commit (this=this@entry=0x7fbcf9e5bae0) at /usr/src/debug/baloo5-5.54.0-1.1.x86_64/src/engine/transaction.cpp:269
Comment 2 Nate Graham 2019-02-05 21:15:23 UTC

*** This bug has been marked as a duplicate of bug 357206 ***
Comment 3 Valerii Malov 2019-03-13 21:50:40 UTC
Git commit eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d by Valerii Malov.
Committed on 13/03/2019 at 21:50.
Pushed by valeriymalov into branch 'master'.

Baloo engine: treat every non-success code as a failure

Summary:
Treating only MDB_NOTFOUND as an error leads to use of uninitliazed
pointers and handle IDs in other cases (e.g. when get fails with
MDB_BAD_TXN) and wreaks havoc in the application.
Related: bug 361186, bug 390823, bug 372880, bug 395888, bug 367480

Reviewers: #baloo, bruns, poboiko

Reviewed By: #baloo, bruns

Subscribers: cullmann, ngraham, bruns, kde-frameworks-devel, #baloo

Tags: #frameworks, #baloo

Differential Revision: https://phabricator.kde.org/D18664

M  +12   -9    src/engine/database.cpp
M  +26   -17   src/engine/documentdatadb.cpp
M  +30   -22   src/engine/documentdb.cpp
M  +30   -22   src/engine/documentiddb.cpp
M  +25   -16   src/engine/documenttimedb.cpp
M  +0    -1    src/engine/documenturldb.cpp
M  +4    -3    src/engine/documenturldb.h
M  +4    -5    src/engine/fsutils.cpp
M  +28   -15   src/engine/idfilenamedb.cpp
M  +22   -13   src/engine/idtreedb.cpp
M  +37   -29   src/engine/mtimedb.cpp
M  +0    -2    src/engine/phraseanditerator.cpp
M  +24   -19   src/engine/positiondb.cpp
M  +31   -27   src/engine/postingdb.cpp
M  +47   -13   src/engine/transaction.cpp
M  +4    -4    src/engine/transaction.h
M  +3    -2    src/file/extractorprocess.cpp
M  +5    -5    src/file/fileindexscheduler.cpp
M  +5    -4    src/file/indexcleaner.cpp
M  +0    -1    src/file/main.cpp
M  +1    -1    src/file/metadatamover.cpp

https://commits.kde.org/baloo/eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d