Version: 1.5 (using KDE KDE 3.1) Installed from: Debian stable Packages OS: Linux This is on debian/testing with the stable 3.1 debs from download.kde.org. The packages were compiled against debian/woody, so that can't be ruled out as an issue. This has happened several times since I installed kmail1.5+kde3.1. When I'm deleting a string of emails rapidly soon after starting kmail, kmail will abruptly crash. The mail is usually spam with html. I can't confirm that it's always an html email that I'm deleting, but I noticed that the two backtraces I kept both contain the khtml::Loader::qt_invoke symbol. When I restart kmail the deleted mail is still in the inbox, since it hasn't been cleaned up. If I try to delete the same emails over again in the same method as the first time it fails. Kmail is not configured to fetch http references. Here is the backtrace: (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 1024 (LWP 5888)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x412e4609 in wait4 () from /lib/libc.so.6 #0 0x412e4609 in wait4 () from /lib/libc.so.6 #1 0x41359dd0 in __check_rhosts_file () from /lib/libc.so.6 #2 0x411b0eeb in waitpid () from /lib/libpthread.so.0 #3 0x409996ea in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4 #4 0x411aea44 in pthread_sighandler () from /lib/libpthread.so.0 #5 0x4126d518 in sigaction () from /lib/libc.so.6 #6 0x401a1392 in khtml::Loader::servePendingRequests () from /usr/lib/libkhtml.so.4 #7 0x401a3a1f in khtml::Loader::qt_invoke () from /usr/lib/libkhtml.so.4 #8 0x40ccdef9 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #9 0x40f2ea93 in QSignal::signal () from /usr/lib/libqt-mt.so.3 #10 0x40ce35b5 in QSignal::activate () from /usr/lib/libqt-mt.so.3 #11 0x40ce8a63 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3 #12 0x40c7bb53 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #13 0x40c7b954 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #14 0x4093a48a in KApplication::notify () from /usr/lib/libkdecore.so.4 #15 0x40c5e383 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #16 0x40c4037c in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #17 0x40c8d31e in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #18 0x40c8d27b in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #19 0x40c7bcaa in QApplication::exec () from /usr/lib/libqt-mt.so.3 #20 0x08175fe2 in KDialog::marginHint () #21 0x4125d0bf in __libc_start_main () from /lib/libc.so.6
I mistyped something: "If I try to delete the same emails over again in the same method as the first time it fails." What I meant was that it "fails to crash", meaning that I can't reproduce it with the same emails.
*** This bug has been marked as a duplicate of 53605 ***