Bug 145169

Summary:	Crash while deleting mails
Product:	[Applications] kmail	Reporter:	Michael Seiwert <michael.seiwert>
Component:	IMAP	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	bjoern
Priority:	NOR
Version:	1.9.6
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:

Description Michael Seiwert 2007-05-08 07:55:41 UTC

Version:           1.9.6 (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc version 4.1.2 20061115 (prerelease) (SUSE Linux) 
OS:                Linux

This crash happened as I deleted about 10 Mails. There was high network traffic so deleting the mails was very slow. Please see attached bt.

Comment 1 Michael Seiwert 2007-05-08 07:56:06 UTC

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1250036016 (LWP 9808)]
[New Thread -1280820336 (LWP 9812)]
[New Thread -1272427632 (LWP 9811)]
[New Thread -1264034928 (LWP 9810)]
[New Thread -1255642224 (LWP 9809)]
[KCrash handler]
#9  0x00000000 in ?? ()
#10 0xb7e5574b in KMail::ImapJob::slotCopyMessageInfoData (this=0x86733f8, 
    job=0x87654e8, data=@0x858c578)
    at /home/mseiwert/src/svn/kde/kdepim/kmail/imapjob.cpp:600
#11 0xb7e56e91 in KMail::ImapJob::qt_invoke (this=0x86733f8, _id=9, 
    _o=0xbfea1240) at ./kmail/imapjob.moc:133
#12 0xb5f5bf0d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0xb6af3690 in KIO::Job::infoMessage () from /opt/kde35/lib/libkio.so.4
#14 0xb6af36f8 in KIO::SimpleJob::slotInfoMessage ()
   from /opt/kde35/lib/libkio.so.4
#15 0xb6af5710 in KIO::SimpleJob::qt_invoke () from /opt/kde35/lib/libkio.so.4
#16 0xb5f5bf0d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0xb5f5c752 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0xb6ae2a73 in KIO::SlaveInterface::infoMessage ()
   from /opt/kde35/lib/libkio.so.4
#19 0xb6ae37c5 in KIO::SlaveInterface::dispatch ()
   from /opt/kde35/lib/libkio.so.4
#20 0xb6ae25ea in KIO::SlaveInterface::dispatch ()
   from /opt/kde35/lib/libkio.so.4
#21 0xb6adf26c in KIO::Slave::gotInput () from /opt/kde35/lib/libkio.so.4
#22 0xb6adf410 in KIO::Slave::qt_invoke () from /opt/kde35/lib/libkio.so.4
#23 0xb5f5bf0d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0xb5f5ca52 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0xb6297e70 in QSocketNotifier::activated ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0xb5f7a140 in QSocketNotifier::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0xb5efc9b7 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0xb5efd781 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0xb653e602 in KApplication::notify () from /opt/kde35/lib/libkdecore.so.4
#30 0xb5ef1361 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#31 0xb5eabb64 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0xb5f137e0 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0xb5f13676 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#34 0xb5efc56f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#35 0x0804ab62 in main (argc=143996528, argv=0x0)
    at /home/mseiwert/src/svn/kde/kdepim/kmail/main.cpp:110

Comment 2 Michael Seiwert 2007-05-08 07:57:59 UTC

The same backtrace is available in #70 of bug 126715, dunno if its related.

Comment 3 Thomas McGuire 2007-05-08 15:31:47 UTC

Please try the 3.5.7 version as soon as it is released (May 22nd probably) and check if it resolves your problem.

If you know what you are doing, you can also try the 3.5 branch.

Comment 4 Michael Seiwert 2007-05-08 15:57:23 UTC

The error occurs with 3_5_BRANCH checkout from yesterday.

Comment 5 Björn Ruberg 2010-01-06 01:30:55 UTC

Can you still reproduce this?

Comment 6 Myriam Schweingruber 2012-08-19 12:05:17 UTC

Closing for lack of feedback. Kmail1 is currently unmaintained. Please feel free to reopen this report if you can reproduce it with Kmail2 4.8.5 or later and provide a new backtrace.