Bug 131692

Summary:	kmail crashes during automatic mail expire run
Product:	[Unmaintained] kmail	Reporter:	Kai Krakow <kai>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	ralph
Priority:	NOR
Version:	1.9.3
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Kai Krakow 2006-08-02 00:03:21 UTC

Version:           1.9.3 (using KDE 3.5.3, Gentoo)
Compiler:          gcc version 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)
OS:                Linux (i686) release 2.6.17-ck1-r2

KMail crashes when running the automated expire run on my IMAP account (didn't test and don't use other account types).

This is not always reproducable. Sometimes KMail runs fine for some half an hour to hour, sometimes it crashes after seconds. Setting or changing expiry on a folder just to force expiration does not always reproduce the crash.

It worked fine with the kmail-3.5.2-r3 Gentoo package. KMail ran for days there.

Here's a backtrace (sorry, no debug build):

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(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)
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1208502080 (LWP 14370)]
[New Thread -1238516816 (LWP 14402)]
[New Thread -1230124112 (LWP 14401)]
[New Thread -1221731408 (LWP 14400)]
[New Thread -1213338704 (LWP 14399)]
[KCrash handler]
#6  0x45329255 in KMMessage::transferInProgress ()
   from /usr/kde/3.5/lib/libkmailprivate.so
#7  0x453a5aa2 in KMMoveCommand::execute ()
   from /usr/kde/3.5/lib/libkmailprivate.so
#8  0x4533c9ec in KMCommand::slotPostTransfer ()
   from /usr/kde/3.5/lib/libkmailprivate.so
#9  0x4533cae9 in KMCommand::qt_invoke ()
   from /usr/kde/3.5/lib/libkmailprivate.so
#10 0x4533cecb in KMMenuCommand::qt_invoke ()
   from /usr/kde/3.5/lib/libkmailprivate.so
#11 0x4533cf35 in KMMoveCommand::qt_invoke ()
   from /usr/kde/3.5/lib/libkmailprivate.so
#12 0x440b0f54 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#13 0x45155e5d in KMCommand::messagesTransfered ()
   from /usr/kde/3.5/lib/libkmailprivate.so
#14 0x4533c3ba in KMCommand::transferSelectedMsgs ()
   from /usr/kde/3.5/lib/libkmailprivate.so
#15 0x4533c897 in KMCommand::slotStart ()
   from /usr/kde/3.5/lib/libkmailprivate.so
#16 0x4533cace in KMCommand::qt_invoke ()
   from /usr/kde/3.5/lib/libkmailprivate.so
#17 0x4533cecb in KMMenuCommand::qt_invoke ()
   from /usr/kde/3.5/lib/libkmailprivate.so
#18 0x4533cf35 in KMMoveCommand::qt_invoke ()
   from /usr/kde/3.5/lib/libkmailprivate.so
#19 0x440b0f54 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#20 0x4441512d in QSignal::signal () from /usr/qt/3/lib/libqt-mt.so.3
#21 0x440cbc81 in QSignal::activate () from /usr/qt/3/lib/libqt-mt.so.3
#22 0x440d38b3 in QSingleShotTimer::event () from /usr/qt/3/lib/libqt-mt.so.3
#23 0x4404b36f in QApplication::internalNotify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#24 0x4404b51c in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#25 0x43b252e5 in KApplication::notify ()
   from /usr/kde/3.5/lib/libkdecore.so.4
#26 0x4403e60c in QEventLoop::activateTimers ()
   from /usr/qt/3/lib/libqt-mt.so.3
#27 0x43ff608c in QEventLoop::processEvents ()
   from /usr/qt/3/lib/libqt-mt.so.3
#28 0x44061fb1 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#29 0x44061ef6 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#30 0x4404a4cf in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
#31 0x0804a457 in ?? ()
#32 0xbfbc0350 in ?? ()
#33 0xbfbc0260 in ?? ()
#34 0x00000000 in ?? ()

Comment 1 Kai Krakow 2006-08-06 00:55:21 UTC

This is interesting: I upgrade my gentoo packages to kmail-3.5.4 (including kmail 1.9.4) and the problem persisted. Due to some openexr-issue the kioslaves-package was not upgraded. I fixed the openexr issue and emerge kioslaves to the 3.5.4 version of the gentoo package.

It seems the crash problem is gone now. But I am not sure yet. It is just that KMail now runs much longer than with the other version before - no crash yet. I will test longer.

Maybe there's an issue in the older kioslaves? (does it include the imap-stuff?)

Comment 2 Tommi Tervo 2006-08-11 13:19:11 UTC

*** Bug 132241 has been marked as a duplicate of this bug. ***

Comment 3 Kai Krakow 2006-08-11 19:57:33 UTC

My kmail ran for 3 days now without crash since I recompiled and upgraded the gentoo kioslaves package. Although this package does not seem to contain kio_imap or other related stuff (pop3, cached imap) this fixed the problem somehow. At least this is true for letting it do the expire job. I did not try to delete or move larger amounts of mail as the reporter of #132241 did.

Comment 4 Tommi Tervo 2006-09-14 21:24:00 UTC


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