When I set startupFolder=outbox (which is empty) and set checkmail-startup=false in kmailrc, kmail at least starts.
But if I then klick on the inbox (which contains messages), kmail crashes again.

I have now removed all *.index files and now I can start and use kmail again.

Please tell us what line 102 in /opt/qt3/include/qmemarray.h is.

Subject: Re:  kmail crash on startup in KMFolderMgr::readMsgDict

On Sunday 14 December 2003 18:34, you wrote:
> /opt/qt3/include/qmemarray.h

    type& at( uint i ) const
Line 102==>	{ return (type &)(*(type *)QGArray::at(i*sizeof(type))); }

I use Qt-3.2.3

After upgrading to KDE 3.2 my KMail at work crashes as well on startup. :-(

Last debug messages:

kmail: KMFolderDir creating new CachedImap folder with name Kolab@ares
kmail: KMFolderDir creating new CachedImap folder with name INBOX
kmail: KMFolderDir creating new CachedImap folder with name Calendar
kmail: KMFolderDir creating new CachedImap folder with name Contacts
kmail: KMFolderDir creating new CachedImap folder with name Notes
kmail: KMFolderDir creating new CachedImap folder with name Tasks
kmail: pPopFilter set
DCOP aborting (delayed) call from 'anonymous-17659' to 'kmail'
DCOP: unregister 'kmail'
ERROR: Communication problem with kmail, it probably crashed.


Backtrace:

[New Thread 16384 (LWP 17660)]
0x4209fa86 in waitpid () from /lib/i686/libpthread.so.0
#0  0x4209fa86 in waitpid () from /lib/i686/libpthread.so.0
#1  0x41553a33 in KCrash::defaultCrashHandler(int) (sig=11)
    at /localhome/ingo/cvs/kde/3.2/kdelibs/kdecore/kcrash.cpp:246
#2  0x4209e96c in __pthread_sighandler () from /lib/i686/libpthread.so.0
#3  <signal handler called>
#4  0x41c2f19d in QGListIterator::QGListIterator(QGList const&) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#5  0x402267f9 in QPtrListIterator (this=0xbfffecc0, l=@0x824d000)
    at qptrlist.h:157
#6  0x4026a4fd in KMFolderMgr::readMsgDict(KMMsgDict*, KMFolderDir*, int) (
    this=0x8247318, dict=0x82c05a0, dir=0x824cfc8, pass=1)
    at /localhome/ingo/cvs/kde/3.2/kdepim/kmail/kmfoldermgr.cpp:453
#7  0x4026a5c8 in KMFolderMgr::readMsgDict(KMMsgDict*, KMFolderDir*, int) (
    this=0x8247318, dict=0x82c05a0, dir=0x82496d8, pass=1)
    at /localhome/ingo/cvs/kde/3.2/kdepim/kmail/kmfoldermgr.cpp:453
#8  0x4026a5c8 in KMFolderMgr::readMsgDict(KMMsgDict*, KMFolderDir*, int) (
    this=0x8247318, dict=0x82c05a0, dir=0x8275818, pass=1)
    at /localhome/ingo/cvs/kde/3.2/kdepim/kmail/kmfoldermgr.cpp:453
#9  0x4026a5c8 in KMFolderMgr::readMsgDict(KMMsgDict*, KMFolderDir*, int) (
    this=0x8247318, dict=0x82c05a0, dir=0x8247344, pass=1)
    at /localhome/ingo/cvs/kde/3.2/kdepim/kmail/kmfoldermgr.cpp:453
#10 0x402e7409 in KMKernel::msgDict() (this=0xbffff390)
    at /localhome/ingo/cvs/kde/3.2/kdepim/kmail/kmkernel.cpp:1639
#11 0x4029dc14 in KMMsgList::clear(bool, bool) (this=0x8247fc8, doDelete=true, 
    syncDict=true) at /localhome/ingo/cvs/kde/3.2/kdepim/kmail/kmmsglist.cpp:36
#12 0x40363fe6 in KMFolderIndex::clearIndex(bool, bool) (this=0x8247f00, 
    autoDelete=true, syncDict=true)
    at /localhome/ingo/cvs/kde/3.2/kdepim/kmail/kmfolderindex.cpp:430
#13 0x40223ad6 in KMFolder::remove() (this=0x8247f00)
    at /localhome/ingo/cvs/kde/3.2/kdepim/kmail/kmfolder.cpp:722
#14 0x402ca2ed in KMFolderCachedImap::remove() (this=0x8247f00)
    at /localhome/ingo/cvs/kde/3.2/kdepim/kmail/kmfoldercachedimap.cpp:153
#15 0x40269c3e in KMFolderMgr::removeFolderAux(KMFolder*) (this=0x8247318, 
    aFolder=0x8247f00)
    at /localhome/ingo/cvs/kde/3.2/kdepim/kmail/kmfoldermgr.cpp:314
#16 0x40269d38 in KMFolderMgr::removeDirAux(KMFolderDir*) (this=0x8247318, 
    aFolderDir=0x82496d8)
    at /localhome/ingo/cvs/kde/3.2/kdepim/kmail/kmfoldermgr.cpp:329
#17 0x40269c0b in KMFolderMgr::removeFolderAux(KMFolder*) (this=0x8247318, 
    aFolder=0x824a620)
    at /localhome/ingo/cvs/kde/3.2/kdepim/kmail/kmfoldermgr.cpp:311
#18 0x40269d38 in KMFolderMgr::removeDirAux(KMFolderDir*) (this=0x8247318, 
    aFolderDir=0x8275818)
    at /localhome/ingo/cvs/kde/3.2/kdepim/kmail/kmfoldermgr.cpp:329
#19 0x40269c0b in KMFolderMgr::removeFolderAux(KMFolder*) (this=0x8247318, 
    aFolder=0x82474e0)
    at /localhome/ingo/cvs/kde/3.2/kdepim/kmail/kmfoldermgr.cpp:311
#20 0x40269ac7 in KMFolderMgr::remove(KMFolder*) (this=0x8247318, 
    aFolder=0x82474e0)
    at /localhome/ingo/cvs/kde/3.2/kdepim/kmail/kmfoldermgr.cpp:300
#21 0x402e4410 in KMKernel::cleanupImapFolders() (this=0xbffff390)
    at /localhome/ingo/cvs/kde/3.2/kdepim/kmail/kmkernel.cpp:936
#22 0x402e4001 in KMKernel::init() (this=0xbffff390)
    at /localhome/ingo/cvs/kde/3.2/kdepim/kmail/kmkernel.cpp:880
#23 0x0804a5b9 in main (argc=7, argv=0xbffff5f4)
    at /localhome/ingo/cvs/kde/3.2/kdepim/kmail/main.cpp:101

After adding a debug statement KMail started without crashing. It would probably also have started without crashing if I had simply tried starting it a second time. Unfortunately I can't recreate the situation that lead to the crash.

FWIW, line 157 in qptrlist.h is
    QPtrListIterator(const QPtrList<type> &l) :QGListIterator((QGList &)l) {}

This was temporary and is resolved now, I take it?

I left KMail open when shutting down KDE (thus making it part of session management). On restarting, KMail didn't come up. Worse, it reliably crashes with the following trace:

#5  <signal handler called>
#6  0x401bac5b in KMMsgDict::readFolderIds ()
   from /opt/kde3/lib/libkmailprivate.so.0
#7  0x401dba76 in KMFolderMgr::readMsgDict ()
   from /opt/kde3/lib/libkmailprivate.so.0
#8  0x401dbac2 in KMFolderMgr::readMsgDict ()
   from /opt/kde3/lib/libkmailprivate.so.0
#9  0x40243951 in KMKernel::msgDict () from /opt/kde3/lib/libkmailprivate.so.0
#10 0x401801a9 in KMHeaders::readSortOrder ()
   from /opt/kde3/lib/libkmailprivate.so.0
#11 0x4017bf81 in KMHeaders::updateMessageList ()
   from /opt/kde3/lib/libkmailprivate.so.0
#12 0x40176efa in KMHeaders::setFolder ()
   from /opt/kde3/lib/libkmailprivate.so.0
#13 0x40294597 in KMMainWidget::folderSelected ()
   from /opt/kde3/lib/libkmailprivate.so.0
#14 0x40294219 in KMMainWidget::folderSelected ()
   from /opt/kde3/lib/libkmailprivate.so.0
#15 0x4028ce83 in KMMainWidget::qt_invoke ()
   from /opt/kde3/lib/libkmailprivate.so.0
#16 0x415def37 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0x4016b4f5 in KMFolderTree::folderSelected ()
   from /opt/kde3/lib/libkmailprivate.so.0
#18 0x40167b13 in KMFolderTree::doFolderSelected ()
   from /opt/kde3/lib/libkmailprivate.so.0
#19 0x4029e4fb in KMMainWidget::slotShowStartupFolder ()
   from /opt/kde3/lib/libkmailprivate.so.0
#20 0x4028d4e9 in KMMainWidget::qt_invoke ()
   from /opt/kde3/lib/libkmailprivate.so.0
#21 0x415def37 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x4187d0f5 in QSignal::signal () from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x415f4539 in QSignal::activate () from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0x415f9d90 in QSingleShotTimer::event ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0x41599d64 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0x415999e4 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0x411e4a18 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#28 0x4158cd32 in QEventLoop::activateTimers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0x41554e82 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0x415a7fb1 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#31 0x415a7ef7 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0x41599ed6 in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0x804acb6 in KMKernel::cleanup ()
#34 0x41ca0baf in __libc_start_main () from /lib/libc.so.6

This is KDE 3.2.3 with Qt 3.3. Sorry, this is a release build.

I'm looking for a workaround.

Deleting the .*.{index,ids,sorted} files of a certain subdirectory made the crash go away.

Oh no! I deleted them, so I can't reproduce the crash any more. Hope the backtrace helps somewhat.

Btw: Is KMail not intended for session management?

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

Till, you marked bug 82456 as a dup of this one, but the other way round would have made more sense. Because that other bug tells you *why* this all happens and also points to a bunch of other race conditions in the code involved :)

Raising severity so I remember to look at it soonish.

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

CVS commit by tilladam: 

Be somewhat safer when reading the message serial number dict for a folder
from disk. The format is still not completely safe, but since we haven't
had any more reports of this problem it seems to have been intermittent
and there is not much more we can do. Folders can be very large, so any
kind of a maximum size would have to be so large as to be useless. If 
anyone has a patch to improve this further, send it my way.

BUG: 70406


  M +4 -3      kmfoldermgr.cpp   1.105


--- kdepim/kmail/kmfoldermgr.cpp  #1.104:1.105
@@ -510,5 +510,6 @@ void KMFolderMgr::readMsgDict(KMMsgDict 
              {
                if (pass == 1) {
-                 dict->readFolderIds(folder);
+                 if ( !dict->readFolderIds(folder) )
+                   invalidateFolder(dict, folder);
                } else if (pass == 2) {
                  if (!dict->hasFolderIds(folder)) {