Bug 403483 - Baloo crashed
Summary: Baloo crashed
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-22 04:14 UTC by Reinhard Auner
Modified: 2019-02-05 19:57 UTC (History)
2 users (show)

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


Attachments
New crash information added by DrKonqi (7.85 KB, text/plain)
2019-01-23 18:08 UTC, Reinhard Auner
Details
New crash information added by DrKonqi (4.68 KB, text/plain)
2019-01-25 15:27 UTC, Reinhard Auner
Details
New crash information added by DrKonqi (4.70 KB, text/plain)
2019-01-27 11:48 UTC, Reinhard Auner
Details
New crash information added by DrKonqi (4.56 KB, text/plain)
2019-02-05 16:04 UTC, Reinhard Auner
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Reinhard Auner 2019-01-22 04:14:29 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:

I had open Google Chrome and VM Virtual Box, when suddenly, Baloo crashed.

-- 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 0x7f116fe74100 (LWP 2220))]

Thread 3 (Thread 0x7f116490a700 (LWP 3652)):
[KCrash Handler]
#6  0x00007f116d8a3130 in __memcpy_ssse3 () from /lib64/libc.so.6
#7  0x00007f116ee65a93 in memcpy (__len=2067, __src=<optimized out>, __dest=<optimized out>) at /usr/include/bits/string_fortified.h:34
#8  Baloo::PostingCodec::decode (this=this@entry=0x7f1164909997, arr=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/codecs/postingcodec.cpp:42
#9  0x00007f116ee56f64 in Baloo::PostingDB::get (this=this@entry=0x7f1164909a80, term=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/postingdb.cpp:100
#10 0x00007f116ee63180 in Baloo::WriteTransaction::commit (this=0x7ed158031bf0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/writetransaction.cpp:259
#11 0x00007f116ee5c4c2 in Baloo::Transaction::commit (this=this@entry=0x7f1164909b90) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/transaction.cpp:262
#12 0x0000562ff98496cd in Baloo::NewFileIndexer::run (this=0x562ffc097fb0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/file/newfileindexer.cpp:75
#13 0x00007f116e2be372 in QThreadPoolThread::run (this=0x562ffbbd0a80) at thread/qthreadpool.cpp:99
#14 0x00007f116e2c10ce in QThreadPrivate::start (arg=0x562ffbbd0a80) at thread/qthread_unix.cpp:368
#15 0x00007f116c8aa559 in start_thread () from /lib64/libpthread.so.0
#16 0x00007f116d86381f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f1165452700 (LWP 2225)):
#0  0x00007f116d85907b in poll () from /lib64/libc.so.6
#1  0x00007f1169f011c9 in g_main_context_poll (priority=<optimized out>, n_fds=1, fds=0x7f1160002de0, timeout=<optimized out>, context=0x7f1160000be0) at gmain.c:4169
#2  g_main_context_iterate (context=context@entry=0x7f1160000be0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3863
#3  0x00007f1169f012dc in g_main_context_iteration (context=0x7f1160000be0, may_block=may_block@entry=1) at gmain.c:3929
#4  0x00007f116e4e4c0b in QEventDispatcherGlib::processEvents (this=0x7f1160000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x00007f116e48d09a in QEventLoop::exec (this=this@entry=0x7f1165451ca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x00007f116e2bc4da in QThread::exec (this=this@entry=0x7f116f989d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:515
#7  0x00007f116f719985 in QDBusConnectionManager::run (this=0x7f116f989d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178
#8  0x00007f116e2c10ce in QThreadPrivate::start (arg=0x7f116f989d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:368
#9  0x00007f116c8aa559 in start_thread () from /lib64/libpthread.so.0
#10 0x00007f116d86381f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f116fe74100 (LWP 2220)):
#0  0x00007f116d85907b in poll () from /lib64/libc.so.6
#1  0x00007f1169f011c9 in g_main_context_poll (priority=<optimized out>, n_fds=1, fds=0x562ffba33b20, timeout=<optimized out>, context=0x562ffba2b260) at gmain.c:4169
#2  g_main_context_iterate (context=context@entry=0x562ffba2b260, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3863
#3  0x00007f1169f012dc in g_main_context_iteration (context=0x562ffba2b260, may_block=may_block@entry=1) at gmain.c:3929
#4  0x00007f116e4e4bef in QEventDispatcherGlib::processEvents (this=0x562ffba2a8d0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#5  0x00007f116e48d09a in QEventLoop::exec (this=this@entry=0x7ffe6c294890, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x00007f116e4959e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1289
#7  0x0000562ff984121c 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 2220) detached]

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

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

Reported using DrKonqi
Comment 1 Reinhard Auner 2019-01-23 18:08:27 UTC
Created attachment 117622 [details]
New crash information added by DrKonqi

baloo_file (5.45.0) using Qt 5.9.4

- What I was doing when the application crashed:

I had open amarok and Google Chrome, when suddenly, Baloo crashed unexpectedly.

-- Backtrace (Reduced):
#7  0x00007fd8b187da93 in memcpy (__len=2067, __src=<optimized out>, __dest=<optimized out>) at /usr/include/bits/string_fortified.h:34
#8  Baloo::PostingCodec::decode (this=this@entry=0x7fd8a7321997, arr=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/codecs/postingcodec.cpp:42
#9  0x00007fd8b186ef64 in Baloo::PostingDB::get (this=this@entry=0x7fd8a7321a80, term=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/postingdb.cpp:100
#10 0x00007fd8b187b180 in Baloo::WriteTransaction::commit (this=0x7f98980302b0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/writetransaction.cpp:259
#11 0x00007fd8b18744c2 in Baloo::Transaction::commit (this=this@entry=0x7fd8a7321b90) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/transaction.cpp:262
Comment 2 Reinhard Auner 2019-01-25 15:27:18 UTC
Created attachment 117656 [details]
New crash information added by DrKonqi

baloo_file (5.45.0) using Qt 5.9.4

- What I was doing when the application crashed:

I had open amarok and Google Chrome when suddenly, Baloo crashed.

-- Backtrace (Reduced):
#7  0x00007f641aedda93 in memcpy (__len=2067, __src=<optimized out>, __dest=<optimized out>) at /usr/include/bits/string_fortified.h:34
#8  Baloo::PostingCodec::decode (this=this@entry=0x7f6410981997, arr=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/codecs/postingcodec.cpp:42
#9  0x00007f641aecef64 in Baloo::PostingDB::get (this=this@entry=0x7f6410981a80, term=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/postingdb.cpp:100
#10 0x00007f641aedb180 in Baloo::WriteTransaction::commit (this=0x7f2404001dc0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/writetransaction.cpp:259
#11 0x00007f641aed44c2 in Baloo::Transaction::commit (this=this@entry=0x7f6410981b90) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/transaction.cpp:262
Comment 3 Reinhard Auner 2019-01-27 11:48:10 UTC
Created attachment 117671 [details]
New crash information added by DrKonqi

baloo_file (5.45.0) using Qt 5.9.4

- What I was doing when the application crashed:

I was surfing the internet with Google Chrome and had open amarok, when Baloo crashed.

-- Backtrace (Reduced):
#7  0x00007fb0374d5a93 in memcpy (__len=2067, __src=<optimized out>, __dest=<optimized out>) at /usr/include/bits/string_fortified.h:34
#8  Baloo::PostingCodec::decode (this=this@entry=0x7fb02cf79997, arr=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/codecs/postingcodec.cpp:42
#9  0x00007fb0374c6f64 in Baloo::PostingDB::get (this=this@entry=0x7fb02cf79a80, term=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/postingdb.cpp:100
#10 0x00007fb0374d3180 in Baloo::WriteTransaction::commit (this=0x7f7020030b30) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/writetransaction.cpp:259
#11 0x00007fb0374cc4c2 in Baloo::Transaction::commit (this=this@entry=0x7fb02cf79b90) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/transaction.cpp:262
Comment 4 Reinhard Auner 2019-02-05 16:04:13 UTC
Created attachment 117842 [details]
New crash information added by DrKonqi

baloo_file (5.45.0) using Qt 5.9.4

- What I was doing when the application crashed:

I downloaded a photo from flickr, had open Google Chrome, nothing else, Baloo crashed.

-- Backtrace (Reduced):
#7  0x00007f9ac7b5da93 in memcpy (__len=2067, __src=<optimized out>, __dest=<optimized out>) at /usr/include/bits/string_fortified.h:34
#8  Baloo::PostingCodec::decode (this=this@entry=0x7f9abd53d997, arr=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/codecs/postingcodec.cpp:42
#9  0x00007f9ac7b4ef64 in Baloo::PostingDB::get (this=this@entry=0x7f9abd53da80, term=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/postingdb.cpp:100
#10 0x00007f9ac7b5b180 in Baloo::WriteTransaction::commit (this=0x7f5ab002e9e0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/writetransaction.cpp:259
#11 0x00007f9ac7b544c2 in Baloo::Transaction::commit (this=this@entry=0x7f9abd53db90) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/transaction.cpp:262
Comment 5 Nate Graham 2019-02-05 19:57:00 UTC

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