Bug 353707 - Baloo uses 100% CPU, does not respond to balooctl disable, and crashes on balooctl enable
Summary: Baloo uses 100% CPU, does not respond to balooctl disable, and crashes on bal...
Status: RESOLVED DUPLICATE of bug 341990
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-10-09 08:26 UTC by basti
Modified: 2015-10-10 21:54 UTC (History)
0 users

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 basti 2015-10-09 08:26:37 UTC
Application: baloo_file (5.6.2)

Qt Version: 5.4.1
Operating System: Linux 3.19.0-30-generic x86_64
Distribution: Ubuntu 15.04

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

I noticed baloo_file using 100% CPU (over several days). 

I read that this may be fixed by `balooctl disable; balooctl enable`. `balooctl disable` took a long time, and baloo_file was still using 100% CPU. 

Thus I killed it (right click in System Monitor: Signal TERM). This stopped baloo_file.

Then I tried re-enabling it using `balooctl_enable`, which listed a bunch of files, and then produced the attached crash.

After a few minutes, baloo_file came back on its own, and consumed 100% CPU again. However, this time, every instance of baloo_file only lasted for a few seconds until it was replaced by another instance (different PID). Thus I guess it's crashing over and over.

- Unusual behavior I noticed:

baloo_file uses 100% CPU
does not stop on `balooctl disable`
and crashes on `balooctl enable`

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File (baloo_file), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb15e5af800 (LWP 31551))]

Thread 2 (Thread 0x7fb14bba7700 (LWP 31553)):
#0  0x00007fb15ae578dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fb159d3fb72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007fb159d4164f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007fb14df0b099 in QXcbEventReader::run (this=0x215c3e0) at qxcbconnection.cpp:1105
#4  0x00007fb15b6eeb0e in QThreadPrivate::start (arg=0x215c3e0) at thread/qthread_unix.cpp:337
#5  0x00007fb15ab456aa in start_thread (arg=0x7fb14bba7700) at pthread_create.c:333
#6  0x00007fb15ae62eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fb15e5af800 (LWP 31551)):
[KCrash Handler]
#6  getint2 (c=9, p=<optimized out>) at ../common/unaligned.h:50
#7  ChertTable::find_in_block (p=p@entry=0x63a7750 <error: Cannot access memory at address 0x63a7750>, key=..., leaf=leaf@entry=false, c=11) at ../backends/chert/chert_table.cc:474
#8  0x00007fb15d586db3 in ChertTable::find (this=0x2198f18, C_=0x22cdd10) at ../backends/chert/chert_table.cc:508
#9  0x00007fb15d560a31 in ChertCursor::find_entry (this=0x23cbd90, key="\000\330\000\000\004") at ../backends/chert/chert_cursor.cc:214
#10 0x00007fb15d58d7b3 in ChertValueManager::get_chunk_containing_did (this=this@entry=0x2199478, slot=slot@entry=0, did=4, chunk="") at ../backends/chert/chert_values.cc:164
#11 0x00007fb15d5910d3 in ChertValueManager::get_value (this=0x2199478, did=4, slot=0) at ../backends/chert/chert_values.cc:476
#12 0x00007fb15d57122a in ChertDocument::do_get_value (this=<optimized out>, slot=<optimized out>) at ../backends/chert/chert_document.cc:40
#13 0x00007fb15d4e1a62 in Xapian::Document::Internal::get_value (this=0x30a88d0, slot=slot@entry=0) at ../api/omdocument.cc:279
#14 0x00007fb15d4e1a7c in Xapian::Document::get_value (this=this@entry=0x7fffef359d00, slot=slot@entry=0) at ../api/omdocument.cc:59
#15 0x00007fb15d8a910a in Baloo::XapianDocument::value (this=this@entry=0x7fffef359d00, slot=slot@entry=0) at ../../../src/xapian/xapiandocument.cpp:133
#16 0x000000000041e4c4 in Baloo::BasicIndexingQueue::shouldIndex (this=this@entry=0x2330e70, file=..., mimetype=...) at ../../../src/file/basicindexingqueue.cpp:142
#17 0x000000000041f0a5 in Baloo::BasicIndexingQueue::process (this=this@entry=0x2330e70, file=..., flags=...) at ../../../src/file/basicindexingqueue.cpp:97
#18 0x000000000041f65c in Baloo::BasicIndexingQueue::processNextIteration (this=0x2330e70) at ../../../src/file/basicindexingqueue.cpp:79
#19 0x00007fb15b95e73a in QObject::event (this=0x2330e70, e=<optimized out>) at kernel/qobject.cpp:1245
#20 0x00007fb15c236b2c in QApplicationPrivate::notify_helper (this=0x2144540, receiver=0x2330e70, e=0x22abbb0) at kernel/qapplication.cpp:3720
#21 0x00007fb15c23c000 in QApplication::notify (this=0x7fffef35a530, receiver=0x2330e70, e=0x22abbb0) at kernel/qapplication.cpp:3503
#22 0x00007fb15b92cc2b in QCoreApplication::notifyInternal (this=0x7fffef35a530, receiver=0x2330e70, event=event@entry=0x22abbb0) at kernel/qcoreapplication.cpp:935
#23 0x00007fb15b92ec9b in sendEvent (event=0x22abbb0, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:228
#24 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x21422c0) at kernel/qcoreapplication.cpp:1552
#25 0x00007fb15b92f298 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1410
#26 0x00007fb15b985843 in postEventSourceDispatch (s=0x2176050) at kernel/qeventdispatcher_glib.cpp:271
#27 0x00007fb155831c3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007fb155831f20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007fb155831fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x00007fb15b985c57 in QEventDispatcherGlib::processEvents (this=0x2179a80, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#31 0x00007fb15b92a3e2 in QEventLoop::exec (this=this@entry=0x7fffef35a3a0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#32 0x00007fb15b93202c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1188
#33 0x00007fb15bc7131c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1510
#34 0x00007fb15c2327a5 in QApplication::exec () at kernel/qapplication.cpp:2956
#35 0x0000000000417477 in main (argc=1, argv=<optimized out>) at ../../../src/file/main.cpp:101

Reported using DrKonqi
Comment 1 Christoph Feck 2015-10-10 21:54:35 UTC

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