Bug 123431

Summary: kmail crashes when i set an expire time on any folder with large number of messages
Product: [Applications] kmail Reporter: Ciaran Farrell <cfarrell1980>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: 1.9.1   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: KMail crash report

Description Ciaran Farrell 2006-03-11 14:47:54 UTC 
Version:           1.9.1 (using KDE KDE 3.5.1)
Installed from:    SuSE RPMs
Compiler:          gcc version 4.0.2 20050901 (prerelease) (SUSE Linux) Using built-in specs.
Target: i586-suse-linux
Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib --enable-languages=c,c++,objc,f95,java,ada --disable-checking --with-gxx-include-dir=/usr/include/c++/4.0.2 --enable-java-awt=gtk --disable-libjava-multilib --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit --without-system-libunwind --host=i586-suse-linux
Thread model: posix
OS:                Linux

I was thinking of not submitting this bug as there are already a number of bug reports about large folders crashing KMail. However, other bug reporters were dealing with over 20 000 mails and my Spam folder only has, maybe 3000 mails. The problem arose when I wanted to automatically delete mails after a certain period of time (by right-clicking on the Spam folder and clicking (German -> >Aufbewahrungsfrist setzen) -> delete after time limit. The default is 30 days but I changed this to 5 days for unread messages and 5 days for read messages. After clicking on ok, the application immediately crashed. When I re-started the application I noticed that the changes I had made (i.e. ticking the boxes to enable the time limits and changing the defaults from 30 days to 5 days for read and unread messages) had NOT been saved.

I'm not sure if this has anything to do with the number of messages in the folder -> on a general note, there are a number of bug reports for filters on large folders (imap, local etc). My backtrace was pretty much useless.
Comment 1 Thiago Macieira 2006-03-12 16:02:01 UTC 
I have folders with more emails than that that don't cause crashes.

We really need a good backtrace or a way of reproducing this. Otherwise, the report is useless.
Comment 2 Ciaran Farrell 2006-03-12 16:11:24 UTC 
Created attachment 15080 [details]
KMail crash report

Not sure if this is any good
Comment 3 Thiago Macieira 2006-03-12 19:46:38 UTC 
Pasting the backtrace:
[KCrash handler]
#6  0x00000011 in ?? ()
#7  0x42802da6 in KMMoveCommand::execute ()
   from /opt/kde3/lib/libkmailprivate.so
#8  0x4277b16b in KMCommand::slotPostTransfer ()
   from /opt/kde3/lib/libkmailprivate.so
#9  0x42800226 in KMCommand::qt_invoke () from /opt/kde3/lib/libkmailprivate.so
#10 0x4280051b in KMMenuCommand::qt_invoke ()
   from /opt/kde3/lib/libkmailprivate.so
#11 0x428005b3 in KMMoveCommand::qt_invoke ()
   from /opt/kde3/lib/libkmailprivate.so
#12 0x410e0a49 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0x42776d32 in KMCommand::messagesTransfered ()
   from /opt/kde3/lib/libkmailprivate.so
#14 0x427ffd8d in KMCommand::transferSelectedMsgs ()
   from /opt/kde3/lib/libkmailprivate.so
#15 0x427ffff7 in KMCommand::slotStart () from /opt/kde3/lib/libkmailprivate.so
#16 0x42800238 in KMCommand::qt_invoke () from /opt/kde3/lib/libkmailprivate.so
#17 0x4280051b in KMMenuCommand::qt_invoke ()
   from /opt/kde3/lib/libkmailprivate.so
#18 0x428005b3 in KMMoveCommand::qt_invoke ()
   from /opt/kde3/lib/libkmailprivate.so
#19 0x410e0a49 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x414225d2 in QSignal::signal () from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0x410fd66b in QSignal::activate () from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x41104fc3 in QSingleShotTimer::event ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x41080d41 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0x410816b9 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0x40d8760e in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#26 0x41075ab8 in QEventLoop::activateTimers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0x4102ef4f in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0x41097c39 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0x41097b36 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0x4108068f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
Comment 4 Thiago Macieira 2006-03-12 19:52:03 UTC 

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