Bug 368352 - baloo crashes immediatly
Summary: baloo crashes immediatly
Status: RESOLVED DUPLICATE of bug 367480
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-06 18:58 UTC by Tom Chiverton
Modified: 2016-09-11 19:55 UTC (History)
2 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 Tom Chiverton 2016-09-06 18:58:52 UTC
Application: baloo_file (5.18.0)

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

-- Information about the crash:
- What I was doing when the application crashed:
running balloctl restart at command line or logging in.

(some more text to keep the wizard happy)

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 0x7f7f1990b8c0 (LWP 6670))]

Thread 2 (Thread 0x7f7dce85d700 (LWP 6671)):
[KCrash Handler]
#6  Baloo::getVarint32Ptr (value=0x7f7dce85c904, limit=0x7f7f311bab17 <error: Cannot access memory at address 0x7f7f311bab17>, p=0x0) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/codecs/coding.h:120
#7  Baloo::getDifferentialVarInt32 (p=0x0, p@entry=0x7f7f18aea51c <QVector<QPair<unsigned long long, QByteArray> >::reallocData(int, int, QFlags<QArrayData::AllocationOption>)+28> "\203\370\001@\017\227\305\205\322\017\204E\001", limit=limit@entry=0x7f7f311bab17 <error: Cannot access memory at address 0x7f7f311bab17>, values=values@entry=0x7f7dce85c968) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/codecs/coding.cpp:158
#8  0x00007f7f18b066b5 in Baloo::PositionCodec::decode (this=this@entry=0x7f7dce85c9cf, arr=...) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/codecs/positioncodec.cpp:55
#9  0x00007f7f18af0fb4 in Baloo::PositionDB::get (this=this@entry=0x7f7dce85cac0, term=...) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/positiondb.cpp:101
#10 0x00007f7f18b03de4 in Baloo::WriteTransaction::commit (this=<optimized out>) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/writetransaction.cpp:290
#11 0x00007f7f18afb032 in Baloo::Transaction::commit (this=this@entry=0x7f7dce85cba0) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/transaction.cpp:262
#12 0x000000000041bcdd in Baloo::FirstRunIndexer::run (this=0x14c3cd0) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/firstrunindexer.cpp:81
#13 0x00007f7f18419343 in QThreadPoolThread::run (this=0x159cac0) at thread/qthreadpool.cpp:93
#14 0x00007f7f1841c84e in QThreadPrivate::start (arg=0x159cac0) at thread/qthread_unix.cpp:331
#15 0x00007f7f170806fa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#16 0x00007f7f17a29b5d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7f7f1990b8c0 (LWP 6670)):
#0  0x00007f7f17a1de8d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007f7f14bee39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f7f14bee4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f7f18653a7f in QEventDispatcherGlib::processEvents (this=0x14b4570, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#4  0x00007f7f185fadea in QEventLoop::exec (this=this@entry=0x7ffe376e7820, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x00007f7f18602e8c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229
#6  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 355280.

Reported using DrKonqi
Comment 1 Christoph Cullmann 2016-09-11 19:55:44 UTC

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