Bug 374584 - plasmashell crashes when searching in kickoff
Summary: plasmashell crashes when searching in kickoff
Status: RESOLVED DUPLICATE of bug 369092
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.29.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-05 09:39 UTC by Oded Arbel
Modified: 2017-06-16 08:37 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oded Arbel 2017-01-05 09:39:09 UTC
Ever since upgrading to Neon developer edition (5.8.95), plasmashell crashes whenever opening the application launcher and searching. Just browsing the application launcher works fine.

When I reproduce the problem under GDB, I get this error and this stack trace:

Thread 13 "GlobalQueue[02]" received signal SIGBUS, Bus error.
[Switching to Thread 0x7fff1bfff700 (LWP 22366)]
__memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:238
238     ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S: No such file or directory.
(gdb) bt
#0  __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:238
#1  0x00007ffff2e42520 in QByteArray::QByteArray(char const*, int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x00007fff29d21427 in DBPostingIterator::DBPostingIterator (this=0x7fff14022360, data=<optimized out>, size=<optimized out>) at /workspace/build/src/engine/postingdb.cpp:177
#3  0x00007fff29d21501 in Baloo::PostingDB::iter (this=this@entry=0x7fff1bffe4a0, term=...) at /workspace/build/src/engine/postingdb.cpp:169
#4  0x00007fff29d2baba in Baloo::Transaction::postingIterator (this=this@entry=0x7fff1bffe8c0, query=...) at /workspace/build/src/engine/transaction.cpp:294
#5  0x00007fff2a182592 in Baloo::SearchStore::constructQuery (this=this@entry=0x7fff1bffe9b0, tr=tr@entry=0x7fff1bffe8c0, term=...) at /workspace/build/src/lib/searchstore.cpp:189
#6  0x00007fff2a18282a in Baloo::SearchStore::constructQuery (this=this@entry=0x7fff1bffe9b0, tr=tr@entry=0x7fff1bffe8c0, term=...) at /workspace/build/src/lib/searchstore.cpp:163
#7  0x00007fff2a183780 in Baloo::SearchStore::exec (this=this@entry=0x7fff1bffe9b0, term=..., offset=0, limit=10, sortResults=<optimized out>) at /workspace/build/src/lib/searchstore.cpp:75
#8  0x00007fff2a171f3f in Baloo::Query::exec (this=this@entry=0x7fff1bffea90) at /workspace/build/src/lib/query.cpp:210
#9  0x00007fff2e09d4e4 in SearchRunner::match (this=this@entry=0x409ef50, context=..., type=..., category=...) at /workspace/build/runners/baloo/baloosearchrunner.cpp:111
#10 0x00007fff2e09e421 in SearchRunner::match (this=0x409ef50, context=...) at /workspace/build/runners/baloo/baloosearchrunner.cpp:177
#11 0x00007fff40eed538 in Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () from /usr/lib/x86_64-linux-gnu/libKF5Runner.so.5
#12 0x00007fff40630827 in ThreadWeaver::Executor::run(QSharedPointer<ThreadWeaver::JobInterface> const&, ThreadWeaver::Thread*) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#13 0x00007fff4062f350 in ThreadWeaver::Job::execute(QSharedPointer<ThreadWeaver::JobInterface> const&, ThreadWeaver::Thread*) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#14 0x00007fff4062eb40 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#15 0x00007ffff2e3eb98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007ffff1ce46ba in start_thread (arg=0x7fff1bfff700) at pthread_create.c:333
#17 0x00007ffff274b82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

I have a similar issue in krunner, which I haven't reprod under GDB yet, but I believe it has the same cause.

After running `balooctl disable`, the crash does not happen anymore, neither in Kickoff nor in KRunner.

I'm currently running the Neon debian package version 5.29.0+p16.04+git20170104.0753-0
Comment 1 Marco Martin 2017-06-16 08:37:45 UTC

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