crash in KMAcctCachedImap::processNewMail

[LimCore]

on ubuntu 8.04 amd64
ii kmail 4:3.5.10-0ubuntu1~hardy2

[Thread debugging using libthread_db enabled]
[New Thread 0x7f7b06e086f0 (LWP 20743)]
[New Thread 0x42158950 (LWP 20748)]
[New Thread 0x41957950 (LWP 20747)]
[New Thread 0x41156950 (LWP 20746)]
[New Thread 0x40955950 (LWP 20745)]
[KCrash handler]
#5 KMAcctCachedImap::processNewMail (this=0xcec910, folder=0x13e8130,
    recurse=true) at /usr/share/qt3/include/qshared.h:53
#6 0x00007f7b06718b11 in KMAcctCachedImap::processNewMail (
    this=0x7f7afbf1e9e0)
    at /build/buildd/kdepim-3.5.10/./kmail/kmacctcachedimap.cpp:216
#7 0x00007f7b066b6392 in KMail::AccountManager::processNextCheck (
    this=0x893ba0, _newMail=<value optimized out>)
    at /build/buildd/kdepim-3.5.10/./kmail/accountmanager.cpp:232
#8 0x00007f7b066b6612 in KMail::AccountManager::singleCheckMail (
    this=0x893ba0, account=0xcec910, interactive=<value optimized out>)
    at /build/buildd/kdepim-3.5.10/./kmail/accountmanager.cpp:132
#9 0x00007f7b06642552 in KMAccount::qt_invoke (this=0xcec910, _id=2,
    _o=0x7fff0ee5a620) at ./kmaccount.moc:237
#10 0x00007f7b06700ec9 in KMail::NetworkAccount::qt_invoke (
    this=0x7f7afbf1e9e0, _id=1, _o=0x18261f0) at ./networkaccount.moc:77
#11 0x00007f7b0670c037 in KMail::ImapAccountBase::qt_invoke (this=0xcec910,
    _id=2, _o=0x7fff0ee5a620) at ./imapaccountbase.moc:324
#12 0x00007f7b06716ad3 in KMAcctCachedImap::qt_invoke (this=0xcec910, _id=2,
    _o=0x7fff0ee5a620) at ./kmacctcachedimap.moc:97
#13 0x00007f7aff822fd0 in QObject::activate_signal (this=0x10a0e40,
    clist=0x905670, o=0x7fff0ee5a620) at kernel/qobject.cpp:2359
#14 0x00007f7aff823b4e in QObject::activate_signal (this=0x10a0e40, signal=2)
    at kernel/qobject.cpp:2328
#15 0x00007f7affb9d496 in QTimer::timeout (this=0x10a0e40)
    at .moc/debug-shared-mt/moc_qtimer.cpp:82
#16 0x00007f7aff848d83 in QTimer::event (this=0x10a0e40, e=0x7fff0ee5aac0)
    at kernel/qtimer.cpp:222
#17 0x00007f7aff7bb33a in QApplication::internalNotify (this=0x7fff0ee5b050,
    receiver=0x10a0e40, e=0x7fff0ee5aac0) at kernel/qapplication.cpp:2638
#18 0x00007f7aff7bd093 in QApplication::notify (this=0x7fff0ee5b050,
    receiver=0x10a0e40, e=0x7fff0ee5aac0) at kernel/qapplication.cpp:2361
#19 0x00007f7b00ef16bd in KApplication::notify (this=0x7fff0ee5b050,
    receiver=0x10a0e40, event=0x7fff0ee5aac0)
    at /build/buildd/kdelibs-3.5.10/./kdecore/kapplication.cpp:550
#20 0x00007f7aff74c20e in QApplication::sendEvent (receiver=0x10a0e40,
    event=0x7fff0ee5aac0) at ../include/qapplication.h:523
#21 0x00007f7aff7aeabc in QEventLoop::activateTimers (this=0x66c470)
    at kernel/qeventloop_unix.cpp:559
#22 0x00007f7aff761107 in QEventLoop::processEvents (this=0x66c470, flags=4)
    at kernel/qeventloop_x11.cpp:392
#23 0x00007f7aff7d55bf in QEventLoop::enterLoop (this=0x66c470)
    at kernel/qeventloop.cpp:201
#24 0x00007f7aff7d52ab in QEventLoop::exec (this=0x66c470)
    at kernel/qeventloop.cpp:148
#25 0x00007f7aff7bce00 in QApplication::exec (this=0x7fff0ee5b050)
    at kernel/qapplication.cpp:2761
#26 0x0000000000402eb4 in main (argc=7, argv=<value optimized out>)
    at /build/buildd/kdepim-3.5.10/./kmail/main.cpp:110

[Andreas Wenning (andreas-wenning)]

Can you try to obtain a valgrind log of the crash?
You can run kontact under valgrind using: "valgrind --log-file=kontact.valgrind.log kontact". When it crashes please attach the generated log to the bug report.
When running under valgrind the program will run very slow; that is completely normal (it can even take more than a minute to start).

[Jonathan Thomas (echidnaman)]

e are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!