Bug 172123 - Kmail Crash when deleting multiple read and unread IMAP messages from folder (backtrace included)
Summary: Kmail Crash when deleting multiple read and unread IMAP messages from folder ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail
Classification: Applications
Component: IMAP (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-04 03:06 UTC by Rodney Baker
Modified: 2009-02-17 17:42 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Crash log from 4.1.4 (4.20 KB, text/plain)
2009-02-17 17:40 UTC, Tomi Junnila
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rodney Baker 2008-10-04 03:06:13 UTC
Version:            (using KDE 4.1.2)
OS:                Linux
Installed from:    SuSE RPMs

When deleting multiple messages from an IMAP folder (some read, some unread) Kmail (KDE 4.1.2) crashes. Reproducible about 1 time in 3. 

Backtrace as follows:

Application: KMail (kmail), signal SIGSEGV
[?1034hUsing host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb416ca00 (LWP 2919)]
[KCrash handler]
#6  0xb4a49610 in clearerr () from /lib/libc.so.6
#7  0xb745cd4c in KMFolderMbox::addMsg () from /usr/lib/libkmailprivate.so.4
#8  0xb746d396 in KMFolderImap::slotGetMessagesData ()
   from /usr/lib/libkmailprivate.so.4
#9  0xb74753ab in KMFolderImap::qt_metacall ()
   from /usr/lib/libkmailprivate.so.4
#10 0xb7e0ec19 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb7e0f2e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb5e29549 in KIO::TransferJob::data () from /usr/lib/libkio.so.5
#13 0xb5e29d1e in KIO::TransferJob::slotData () from /usr/lib/libkio.so.5
#14 0xb5e2fb3d in KIO::TransferJob::qt_metacall () from /usr/lib/libkio.so.5
#15 0xb7e0ec19 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb7e0f2e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0xb5edc933 in KIO::SlaveInterface::data () from /usr/lib/libkio.so.5
#18 0xb5edf38e in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#19 0xb5edd107 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#20 0xb5ece9e0 in KIO::Slave::gotInput () from /usr/lib/libkio.so.5
#21 0xb5eced4d in KIO::Slave::qt_metacall () from /usr/lib/libkio.so.5
#22 0xb7e0ec19 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#23 0xb7e0f2e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#24 0xb5dfba17 in KIO::Connection::readyRead () from /usr/lib/libkio.so.5
#25 0xb5dfda0b in KIO::ConnectionPrivate::dequeue () from /usr/lib/libkio.so.5
#26 0xb5dfdace in KIO::Connection::qt_metacall () from /usr/lib/libkio.so.5
#27 0xb7e0856b in QMetaCallEvent::placeMetaCall () from /usr/lib/libQtCore.so.4
#28 0xb7e09971 in QObject::event () from /usr/lib/libQtCore.so.4
#29 0xb4fba1cc in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#30 0xb4fbec79 in QApplication::notify () from /usr/lib/libQtGui.so.4
#31 0xb5ac8d6d in KApplication::notify () from /usr/lib/libkdeui.so.5
#32 0xb7df9cb9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#33 0xb7dfae89 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#34 0xb7dfb0ad in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#35 0xb7e2533f in ?? () from /usr/lib/libQtCore.so.4
#36 0xb496a5d6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#37 0xb496d972 in ?? () from /usr/lib/libglib-2.0.so.0
#38 0x0806a840 in ?? ()
#39 0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()
Comment 1 Rodney Baker 2008-11-02 13:55:47 UTC
This is still occuring in version 1.10.1 KDE 4.1.2 "release 49.1". It is consistently reproducable when selecting and deleting a non-contiguous group of messages from an IMAP (Dovecot) folder for deletion e.g. Shift-select a range of messages, then Ctrl-deselect on message in the middle of the range, then click on the trash can icon. Kmail will crash every time.

Here is the latest backtrace...

Application: KMail (kmail), signal SIGSEGV
[?1034hUsing host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb4229a00 (LWP 20880)]
[KCrash handler]
#6  0xb4b06610 in clearerr () from /lib/libc.so.6
#7  0xb751c01c in KMFolderMbox::addMsg () from /usr/lib/libkmailprivate.so.4
#8  0xb752c666 in KMFolderImap::slotGetMessagesData ()
   from /usr/lib/libkmailprivate.so.4
#9  0xb753467b in KMFolderImap::qt_metacall ()
   from /usr/lib/libkmailprivate.so.4
#10 0xb7ecfc19 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb7ed02e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb5ee7109 in KIO::TransferJob::data () from /usr/lib/libkio.so.5
#13 0xb5ee78de in KIO::TransferJob::slotData () from /usr/lib/libkio.so.5
#14 0xb5eed6fd in KIO::TransferJob::qt_metacall () from /usr/lib/libkio.so.5
#15 0xb7ecfc19 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb7ed02e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0xb5f9b613 in KIO::SlaveInterface::data () from /usr/lib/libkio.so.5
#18 0xb5f9e06e in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#19 0xb5f9bde7 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#20 0xb5f8d7c0 in KIO::Slave::gotInput () from /usr/lib/libkio.so.5
#21 0xb5f8db2d in KIO::Slave::qt_metacall () from /usr/lib/libkio.so.5
#22 0xb7ecfc19 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#23 0xb7ed02e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#24 0xb5eb9c17 in KIO::Connection::readyRead () from /usr/lib/libkio.so.5
#25 0xb5ebbc0b in KIO::ConnectionPrivate::dequeue () from /usr/lib/libkio.so.5
#26 0xb5ebbcce in KIO::Connection::qt_metacall () from /usr/lib/libkio.so.5
#27 0xb7ec956b in QMetaCallEvent::placeMetaCall () from /usr/lib/libQtCore.so.4
#28 0xb7eca971 in QObject::event () from /usr/lib/libQtCore.so.4
#29 0xb50771cc in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#30 0xb507bc79 in QApplication::notify () from /usr/lib/libQtGui.so.4
#31 0xb5b862bd in KApplication::notify () from /usr/lib/libkdeui.so.5
#32 0xb7ebacb9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#33 0xb7ebbe89 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#34 0xb7ebc0ad in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#35 0xb7ee633f in ?? () from /usr/lib/libQtCore.so.4
#36 0xb4a275d6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#37 0xb4a2a972 in ?? () from /usr/lib/libglib-2.0.so.0
#38 0x0806a490 in ?? ()
#39 0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()
Comment 2 Dario Andres 2009-01-20 00:53:25 UTC
If you can reproduce the crash at will in a recent KDE (4.1.4 / 4.2beta2 / 4.2rc1 / 4.2svn / 4.3svn) , may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)
Comment 3 Rodney Baker 2009-01-28 12:44:57 UTC
This appeared fixed in 4.2RC1 but now appears to have regressed after today updating to 4.2.00. Backtrace from most recent crash is as follows:

Application: KMail (kmail), signal SIGSEGV
[?1034h[Thread debugging using libthread_db enabled]

Thread 1 (Thread 0xb41786d0 (LWP 26877)):
[KCrash Handler]
#6  KMail::MessageListView::Widget::getSelectionStats (this=0x82c4b70, selectedSernums=@0xbfcc1938, selectedVisibleSernums=@0xbfcc1934, allSelectedBelongToSameThread=0xbfcc193f, 
    includeCollapsedChildren=<value optimized out>) at /usr/src/debug/kdepim-4.2.0/kmail/messagelistview/widget.cpp:579
#7  0xb78760c6 in KMail::MessageListView::Pane::getSelectionStats (this=0x8236f30, selectedSernums=@0xbfcc1938, selectedVisibleSernums=@0xbfcc1934, allSelectedBelongToSameThread=0xbfcc193f, 
    includeCollapsedChildren=<value optimized out>) at /usr/src/debug/kdepim-4.2.0/kmail/messagelistview/pane.cpp:579
#8  0xb7749357 in KMMainWidget::updateMessageActions (this=0x8236c28) at /usr/src/debug/kdepim-4.2.0/kmail/kmmainwidget.cpp:4288
#9  0xb77639b8 in KMMainWidget::qt_metacall (this=0x8236c28, _c=QMetaObject::InvokeMetaMethod, _id=20, _a=0xbfcc1a08) at /usr/src/debug/kdepim-4.2.0/build/kmail/kmmainwidget.moc:363
#10 0xb6cd8740 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb6cd94c2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb6d13bc7 in QTimer::timeout () from /usr/lib/libQtCore.so.4
#13 0xb6cdf1de in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
#14 0xb6cd31ff in QObject::event () from /usr/lib/libQtCore.so.4
#15 0xb626882c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#16 0xb62706ce in QApplication::notify () from /usr/lib/libQtGui.so.4
#17 0xb7ed068d in KApplication::notify () from /usr/lib/libkdeui.so.5
#18 0xb6cc3a71 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#19 0xb6cf1de6 in ?? () from /usr/lib/libQtCore.so.4
#20 0xb6cee2b0 in ?? () from /usr/lib/libQtCore.so.4
#21 0xb48992d9 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0xb489c85b in ?? () from /usr/lib/libglib-2.0.so.0
#23 0xb489c9d8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#24 0xb6cee208 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#25 0xb63018c5 in ?? () from /usr/lib/libQtGui.so.4
#26 0xb6cc214a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#27 0xb6cc230a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#28 0xb6cc49a5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#29 0xb62686a7 in QApplication::exec () from /usr/lib/libQtGui.so.4
#30 0x0804a5c0 in main (argc=) at /usr/src/debug/kdepim-4.2.0/kmail/main.cpp:146

Will try running it under valgrind to see what it says...
Comment 4 Dario Andres 2009-01-28 12:48:58 UTC
@Rodney: the last backtrace is different from 1st and 2nd. So this is a different crash.
As the original reported crash seems to be fixed I'm going to close this report as WORKSFORME. Please,file a new bug report for the last backtrace
Thanks a lot
Comment 5 Tomi Junnila 2009-02-17 17:40:09 UTC
Created attachment 31408 [details]
Crash log from 4.1.4
Comment 6 Tomi Junnila 2009-02-17 17:42:59 UTC
I get this crash (as in the first two backtraces) with KDE 4.1.4, when deleting single messages from an IMAP folder (Dovecot).