[kde] [Bug 372725] New: baloo_file_extractor taking 100% CPU and IO at login
bugzilla_noreply at kde.org
bugzilla_noreply at kde.org
Mon Nov 21 10:13:27 GMT 2016
https://bugs.kde.org/show_bug.cgi?id=372725
Bug ID: 372725
Summary: baloo_file_extractor taking 100% CPU and IO at login
Product: kde
Version: unspecified
Platform: unspecified
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: carlo.tognetti at europe.com
Target Milestone: ---
Application: baloo_file (5.18.0)
(Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.4.0-49-generic x86_64
Distribution: Ubuntu 16.04.1 LTS
-- Information about the crash:
- What I was doing when the application crashed:
System booted up: OK. Problems begin as soon as I log-in to KDE5
- Unusual behavior I noticed:
Heavy IO load (HDD) and 100% CPU taken by baloo_file_extractor.
.xsession-errors getting bigger and bigger.
Loggin in as another user everything seems to work fine.
- Custom settings of the application:
To be able to work I have to kill (15) baloo_file_extractor.
The problem begun (as far as I can remember) when the system sopped to ask me
for the luks password to decrypt the swap partition.
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 0x7f7b210188c0 (LWP 4716))]
Thread 2 (Thread 0x7f79d5f68700 (LWP 5721)):
#0 0x00007f7b1f13669d in read () at ../sysdeps/unix/syscall-template.S:84
#1 0x00007f7b1c34e740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f7b1c30ae84 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f7b1c30b340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007f7b1c30b4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007f7b1fd707eb in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x00007f7b1fd17b4a in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x0000000000420cd8 in Baloo::FileContentIndexer::run() ()
#8 0x00007f7b1fb362d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9 0x00007f7b1fb397be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f7b1e79d6ba in start_thread (arg=0x7f79d5f68700) at
pthread_create.c:333
#11 0x00007f7b1f14682d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
Thread 1 (Thread 0x7f7b210188c0 (LWP 4716)):
[KCrash Handler]
#6 __memcpy_sse2_unaligned () at
../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:38
#7 0x00007f7b202238da in Baloo::PostingCodec::decode(QByteArray const&) ()
from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#8 0x00007f7b2020f814 in Baloo::PostingDB::get(QByteArray const&) () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#9 0x00007f7b202203c6 in Baloo::WriteTransaction::commit() () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#10 0x00007f7b20218032 in Baloo::Transaction::commit() () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#11 0x00000000004296d5 in Baloo::MetadataMover::removeFileMetadata(QString
const&) ()
#12 0x00007f7b1fd48baf in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x0000000000432f05 in Baloo::PendingFileQueue::removeFileIndex(QString
const&) ()
#14 0x0000000000427856 in Baloo::PendingFileQueue::processCache() ()
#15 0x00007f7b1fd48baf in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f7b1fd555c8 in QTimer::timerEvent(QTimerEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f7b1fd49bb3 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f7b1fd1a36c in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007f7b1fd6f5ed in QTimerInfoList::activateTimers() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007f7b1fd6fb29 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f7b1c30b1a7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f7b1c30b400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f7b1c30b4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007f7b1fd707cf in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00007f7b1fd17b4a in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x00007f7b1fd1fbec in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x000000000041698c in main ()
Possible duplicates by query: bug 356445.
Reported using DrKonqi
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list