Bug 253681 - kmail crashes when quicksearching while the folder is loading
Summary: kmail crashes when quicksearching while the folder is loading
Status: RESOLVED DUPLICATE of bug 261645
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 2.0.89
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-09 18:06 UTC by Anssi Hannula
Modified: 2011-04-17 23:41 UTC (History)
2 users (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 Anssi Hannula 2010-10-09 18:06:15 UTC
Application: kmail (2.0.89)
KDE Platform Version: 4.5.71 (4.6 >= 20101005)
Qt Version: 4.7.0
Operating System: Linux 2.6.36-tmb-desktop-0.rc6.1mdv x86_64
Distribution: "Mandriva Linux 2011.0"

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

I entered a search string into the quick search box while the folder was still loading itself. KMail crashed. I tried to reproduce but didn't manage to.

I've also encountered this issue in the previous stable (of KDE 4.5) KMail series some time ago, but I'm not sure if this one is related.

The crash does not seem to be reproducible.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
[Current thread is 1 (Thread 0x7ffbb2f5a720 (LWP 8188))]

Thread 2 (Thread 0x7ffb9520d710 (LWP 8203)):
#0  0x00007ffbae8f623c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007ffba505e904 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4
#2  0x00007ffbae8f1d25 in start_thread () from /lib64/libpthread.so.0
#3  0x00007ffbb0291efd in clone () from /lib64/libc.so.6
#4  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7ffbb2f5a720 (LWP 8188)):
[KCrash Handler]
#6  0x00007ffbb01ec075 in raise () from /lib64/libc.so.6
#7  0x00007ffbb01ed806 in abort () from /lib64/libc.so.6
#8  0x00007ffbb0ab15d4 in qt_message_output (msgType=<value optimized out>, buf=<value optimized out>) at global/qglobal.cpp:2259
#9  0x00007ffbb0ab179d in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=QtFatalMsg, msg=0x7ffbb0c01d88 "ASSERT: \"%s\" in file %s, line %d", ap=0x7ffff73f0870)
    at global/qglobal.cpp:2305
#10 0x00007ffbb0ab1935 in qFatal (msg=<value optimized out>) at global/qglobal.cpp:2488
#11 0x00007ffbac0f514c in MessageList::Core::ModelPrivate::applyFilterToSubtree (this=0x11c3670, item=0x2499e4f0, parentIndex=...)
    at /usr/src/debug/kdepim-4.5.71svn1183615/messagelist/core/model.cpp:370
#12 0x00007ffbac0f5bbf in MessageList::Core::Model::setFilter (this=0x1081440, filter=<value optimized out>) at /usr/src/debug/kdepim-4.5.71svn1183615/messagelist/core/model.cpp:360
#13 0x00007ffbac11f544 in MessageList::Core::Widget::searchTimerFired (this=<value optimized out>) at /usr/src/debug/kdepim-4.5.71svn1183615/messagelist/core/widgetbase.cpp:1090
#14 0x00007ffbac0e1b0f in MessageList::Core::Widget::qt_metacall (this=0x11dfeb0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7ffff73f0b60)
    at /usr/src/debug/kdepim-4.5.71svn1183615/build/messagelist/moc_widgetbase.cpp:130
#15 0x00007ffbac0e1c10 in MessageList::Widget::qt_metacall (this=0x11dfeb0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7ffff73f0b60)
    at /usr/src/debug/kdepim-4.5.71svn1183615/build/messagelist/moc_widget.cpp:77
#16 0x00007ffbb0bb6fbf in QMetaObject::activate (sender=0x23b602b0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3272
#17 0x00007ffbb0bb67e9 in QObject::event (this=0x23b602b0, e=<value optimized out>) at kernel/qobject.cpp:1175
#18 0x00007ffbb108b664 in QApplicationPrivate::notify_helper (this=0xe5a0e0, receiver=0x23b602b0, e=0x7ffff73f12d0) at kernel/qapplication.cpp:4396
#19 0x00007ffbb10900da in QApplication::notify (this=<value optimized out>, receiver=0x23b602b0, e=0x7ffff73f12d0) at kernel/qapplication.cpp:4277
#20 0x00007ffbb292ac36 in KApplication::notify (this=0x7ffff73f1690, receiver=0x23b602b0, event=0x7ffff73f12d0) at /usr/src/debug/kdelibs-4.5.71svn1183355/kdeui/kernel/kapplication.cpp:311
#21 0x00007ffbb0ba273c in QCoreApplication::notifyInternal (this=0x7ffff73f1690, receiver=0x23b602b0, event=0x7ffff73f12d0) at kernel/qcoreapplication.cpp:732
#22 0x00007ffbb0bd0382 in sendEvent (this=0xe5da70) at kernel/qcoreapplication.h:215
#23 QTimerInfoList::activateTimers (this=0xe5da70) at kernel/qeventdispatcher_unix.cpp:602
#24 0x00007ffbb0bcd198 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#25 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#26 0x00007ffba89caf83 in g_main_dispatch (context=0xe5c920) at gmain.c:2149
#27 g_main_context_dispatch (context=0xe5c920) at gmain.c:2702
#28 0x00007ffba89cb760 in g_main_context_iterate (context=0xe5c920, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2780
#29 0x00007ffba89cb9fd in g_main_context_iteration (context=0xe5c920, may_block=1) at gmain.c:2843
#30 0x00007ffbb0bcd85f in QEventDispatcherGlib::processEvents (this=0xe154e0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415
#31 0x00007ffbb112f8be in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#32 0x00007ffbb0ba1ad2 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#33 0x00007ffbb0ba1d1c in QEventLoop::exec (this=0x7ffff73f1550, flags=...) at kernel/qeventloop.cpp:201
#34 0x00007ffbb0ba619b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#35 0x0000000000402e66 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdepim-4.5.71svn1183615/kmail/main.cpp:145

Reported using DrKonqi
Comment 1 Dario Andres 2010-11-18 20:30:25 UTC
[Comment from a bug triager]
The backtrace in this bug seems a bit related to bug 251876. Regards
Comment 2 Sergio Martins 2011-04-17 23:41:51 UTC
backtrace not entirely equal to 261645, but it shared the buggy part.

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