Bug 109033 - deleting messages too quickly can crash kmail
Summary: deleting messages too quickly can crash kmail
Status: RESOLVED DUPLICATE of bug 107914
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.8.1
Platform: unspecified FreeBSD
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-13 18:47 UTC by mi+kde
Modified: 2007-09-14 12:17 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 mi+kde 2005-07-13 18:47:06 UTC
Version:           1.8.1 (using KDE 3.4.1, compiled sources)
Compiler:          gcc version 3.4.2 [FreeBSD] 20040728
OS:                FreeBSD (i386) release 5.4-STABLE

Going through a thread I did not care for, I kept clicking on the little trash-can icon to get rid off all messages, while KMail was struggling to keep up with me to mark the messages deleted on the imap-server.

Most of the messages I marked for deletion were displayed with the "crossed out" font, but not all, for some reason.

Eventually, it crashed with the following stack:

[Switching to LWP 100140]
0x2a5480d3 in wait4 () from /lib/libc.so.5
#0  0x2a5480d3 in wait4 () from /lib/libc.so.5
#1  0x2a5385f7 in waitpid () from /lib/libc.so.5
#2  0x2a4d80d9 in waitpid () from /usr/lib/libpthread.so.1
#3  0x299a8e81 in KCrash::defaultCrashHandler () from /opt/lib/libkdecore.so.6
#4  0x2a4df0ad in sigaction () from /usr/lib/libpthread.so.1
#5  0xbfbfff94 in ?? ()
#6  0x0000000b in ?? ()
#7  0xbfbfdb90 in ?? ()
#8  0xbfbfd8d0 in ?? ()
#9  0x00000000 in ?? ()
#10 0x2a4decec in sigaction () from /usr/lib/libpthread.so.1
#11 0x28467f47 in KMail::ImapJob::slotGetBodyStructureResult ()
   from /opt/lib/libkmailprivate.so
#12 0x28469141 in KMail::ImapJob::qt_invoke ()
   from /opt/lib/libkmailprivate.so
#13 0x29e043f1 in QObject::activate_signal () from /opt/lib/libqt-mt.so.3
#14 0x29348560 in KIO::Job::result () from /opt/lib/libkio.so.6
#15 0x29331ef6 in KIO::Job::emitResult () from /opt/lib/libkio.so.6
#16 0x2933348d in KIO::SimpleJob::slotFinished () from /opt/lib/libkio.so.6
#17 0x2933601e in KIO::TransferJob::slotFinished () from /opt/lib/libkio.so.6
#18 0x2934a436 in KIO::TransferJob::qt_invoke () from /opt/lib/libkio.so.6
#19 0x29e043f1 in QObject::activate_signal () from /opt/lib/libqt-mt.so.3
#20 0x29e042f6 in QObject::activate_signal () from /opt/lib/libqt-mt.so.3
#21 0x29325c30 in KIO::SlaveInterface::finished () from /opt/lib/libkio.so.6
#22 0x2932423e in KIO::SlaveInterface::dispatch () from /opt/lib/libkio.so.6
#23 0x29323f7f in KIO::SlaveInterface::dispatch () from /opt/lib/libkio.so.6
#24 0x293218bc in KIO::Slave::gotInput () from /opt/lib/libkio.so.6
#25 0x293234fa in KIO::Slave::qt_invoke () from /opt/lib/libkio.so.6
#26 0x29e043f1 in QObject::activate_signal () from /opt/lib/libqt-mt.so.3
#27 0x29e0465e in QObject::activate_signal () from /opt/lib/libqt-mt.so.3
#28 0x2a141216 in QSocketNotifier::activated () from /opt/lib/libqt-mt.so.3
#29 0x29e20e65 in QSocketNotifier::event () from /opt/lib/libqt-mt.so.3
#30 0x29da5149 in QApplication::internalNotify () from /opt/lib/libqt-mt.so.3
#31 0x29da4576 in QApplication::notify () from /opt/lib/libqt-mt.so.3
#32 0x2990d7ed in KApplication::notify () from /opt/lib/libkdecore.so.6
#33 0x29d94e65 in QEventLoop::activateSocketNotifiers ()
   from /opt/lib/libqt-mt.so.3
#34 0x29d4fadb in QEventLoop::processEvents () from /opt/lib/libqt-mt.so.3
#35 0x29db7e07 in QEventLoop::enterLoop () from /opt/lib/libqt-mt.so.3
#36 0x29db7d5e in QEventLoop::exec () from /opt/lib/libqt-mt.so.3
#37 0x29da52a7 in QApplication::exec () from /opt/lib/libqt-mt.so.3
#38 0x0804a612 in main ()
Comment 1 Thiago Macieira 2005-07-14 06:02:28 UTC

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