Bug 363836 - Kontact crashes on Search tools
Summary: Kontact crashes on Search tools
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-06-02 10:26 UTC by MDA
Modified: 2018-02-01 09:48 UTC (History)
1 user (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 MDA 2016-06-02 10:26:06 UTC
Application: kontact (4.14.10)
KDE Platform Version: 4.14.18
Qt Version: 4.8.6
Operating System: Linux 4.1.21-14-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
Steps to replicate:
1. Start a search on a subfolder and wait it to be finished;
2. Go to tools and select Search;
3. The application crashes

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f85705b4800 (LWP 7163))]

Thread 4 (Thread 0x7f8552c33700 (LWP 7164)):
#0  0x00007f8567b1603f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007f856cc9deb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4
#2  0x00007f856cc9dee9 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x00007f8567b120a4 in start_thread () at /lib64/libpthread.so.0
#4  0x00007f856da8dfed in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f855230a700 (LWP 7165)):
#0  0x00007f8567b1603f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007f856ca10b3d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4
#2  0x00007f856ccc5a06 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4
#3  0x00007f8567b120a4 in start_thread () at /lib64/libpthread.so.0
#4  0x00007f856da8dfed in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f84fd8a1700 (LWP 7289)):
#0  0x00007f856da85bbd in poll () at /lib64/libc.so.6
#1  0x00007f8567545e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f8567545f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f856e284fde in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#4  0x00007f856e256d4f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#5  0x00007f856e257045 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#6  0x00007f856e1544df in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x00007f856e156bbf in  () at /usr/lib64/libQtCore.so.4
#8  0x00007f8567b120a4 in start_thread () at /lib64/libpthread.so.0
#9  0x00007f856da8dfed in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f85705b4800 (LWP 7163)):
[KCrash Handler]
#6  0x00007f8508267a3a in MailCommon::SearchPattern::purify(bool) () at /usr/lib64/libmailcommon.so.4
#7  0x00007f85089b82b6 in  () at /usr/lib64/libkmailprivate.so.4
#8  0x00007f85089291c4 in KMMainWidget::slotRequestFullSearchFromQuickSearch() () at /usr/lib64/libkmailprivate.so.4
#9  0x00007f8508a182cf in  () at /usr/lib64/libkmailprivate.so.4
#10 0x00007f856e26c0fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4
#11 0x00007f856ec5c652 in QAction::triggered(bool) () at /usr/lib64/libQtGui.so.4
#12 0x00007f856ec5e003 in QAction::activate(QAction::ActionEvent) () at /usr/lib64/libQtGui.so.4
#13 0x00007f856f087399 in  () at /usr/lib64/libQtGui.so.4
#14 0x00007f856f08b8e9 in  () at /usr/lib64/libQtGui.so.4
#15 0x00007f856fa30015 in KMenu::mouseReleaseEvent(QMouseEvent*) () at /usr/lib64/libkdeui.so.5
#16 0x00007f856ecb1c5a in QWidget::event(QEvent*) () at /usr/lib64/libQtGui.so.4
#17 0x00007f856f08f73b in QMenu::event(QEvent*) () at /usr/lib64/libQtGui.so.4
#18 0x00007f856ec6279c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
#19 0x00007f856ec68e1a in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
#20 0x00007f856f979e9a in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5
#21 0x00007f856e25818d in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4
#22 0x00007f856ec68613 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () at /usr/lib64/libQtGui.so.4
#23 0x00007f856ecda01c in  () at /usr/lib64/libQtGui.so.4
#24 0x00007f856ecd875c in QApplication::x11ProcessEvent(_XEvent*) () at /usr/lib64/libQtGui.so.4
#25 0x00007f856ecff5f2 in  () at /usr/lib64/libQtGui.so.4
#26 0x00007f8567545c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#27 0x00007f8567545ed8 in  () at /usr/lib64/libglib-2.0.so.0
#28 0x00007f8567545f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#29 0x00007f856e284fbe in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#30 0x00007f856ecff6a6 in  () at /usr/lib64/libQtGui.so.4
#31 0x00007f856e256d4f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#32 0x00007f856e257045 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#33 0x00007f856e25c499 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4
#34 0x00000000004037f2 in  ()
#35 0x00007f856d9cab05 in __libc_start_main () at /lib64/libc.so.6
#36 0x0000000000403c97 in _start ()

Reported using DrKonqi
Comment 1 Denis Kurz 2017-06-23 22:16:33 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those Framework-based versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-02-01 09:48:06 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.