Bug 150038

Summary: crash with segmentation fault in imap code if kmail is idle (with backtrace)
Product: [Unmaintained] kmail Reporter: Christian Bornträger <christian>
Component: IMAPAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: jwramsey
Priority: NOR    
Version: 1.9.7   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Christian Bornträger 2007-09-20 14:23:54 UTC
Version:           1.9.7 (using KDE 3.5.7, Debian Package 4:3.5.7.dfsg.1-7 (lenny/sid))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.23-rc6-gc2f82897

Hello,

I use kmail to access several imap servers with lots of folders. Kmail is configured to After some waiting with no action (key press or mouse click) kmail crashes with this backtrace:

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208310080 (LWP 17799)]
[New Thread -1239782512 (LWP 17803)]
[New Thread -1231389808 (LWP 17802)]
[New Thread -1222997104 (LWP 17801)]
[New Thread -1214604400 (LWP 17800)]
[KCrash handler]
#6  0x4c7eb176 in KMMsgBase::storage (this=0x0)
    at /build/buildd/kdepim-3.5.7/./kmail/kmmsgbase.cpp:90
#7  0x4c825381 in KMFolderImap::deleteMessage (this=0x8306768, 
    msgList=@0xbfb53290)
    at /build/buildd/kdepim-3.5.7/./kmail/kmfolderimap.cpp:1848
#8  0x4c825b04 in KMFolderImap::removeMsg (this=0x8306768, 
    msgList=@0xbfb53290, quiet=false)
    at /build/buildd/kdepim-3.5.7/./kmail/kmfolderimap.cpp:305
#9  0x4c771ec6 in KMFolder::removeMsg (this=0x8309088, msgList=@0xbfb53290, 
    imapQuiet=false) at /build/buildd/kdepim-3.5.7/./kmail/kmfolder.cpp:405
#10 0x4c8c8ffc in KMMoveCommand::execute (this=0x8465378)
    at /build/buildd/kdepim-3.5.7/./kmail/kmcommands.cpp:2196
#11 0x4c8ba6f9 in KMCommand::slotPostTransfer (this=0x8465378, 
    result=KMCommand::OK)
    at /build/buildd/kdepim-3.5.7/./kmail/kmcommands.cpp:257
#12 0x4c8c3506 in KMCommand::qt_invoke (this=0x8465378, _id=5, _o=0xbfb533f4)
    at ./kmcommands.moc:148
#13 0x4c8c37eb in KMMenuCommand::qt_invoke (this=0x8465378, _id=5, 
    _o=0xbfb533f4) at ./kmcommands.moc:2801
#14 0x4c8c3877 in KMMoveCommand::qt_invoke (this=0x8465378, _id=5, 
    _o=0xbfb533f4) at ./kmcommands.moc:2987
#15 0x4aa44d23 in QObject::activate_signal (this=0x8465378, clist=0x86425f8, 
    o=0xbfb533f4) at kernel/qobject.cpp:2356
#16 0x4c8ba87e in KMCommand::messagesTransfered (this=0x8465378, 
    t0=KMCommand::OK) at ./kmcommands.moc:126
#17 0x4c8c2801 in KMCommand::transferSelectedMsgs (this=0x8465378)
    at /build/buildd/kdepim-3.5.7/./kmail/kmcommands.cpp:352
#18 0x4c8c2967 in KMCommand::slotStart (this=0x8465378)
    at /build/buildd/kdepim-3.5.7/./kmail/kmcommands.cpp:249
#19 0x4c8c3518 in KMCommand::qt_invoke (this=0x8465378, _id=4, _o=0xbfb53578)
    at ./kmcommands.moc:147
#20 0x4c8c37eb in KMMenuCommand::qt_invoke (this=0x8465378, _id=4, 
    _o=0xbfb53578) at ./kmcommands.moc:2801
#21 0x4c8c3877 in KMMoveCommand::qt_invoke (this=0x8465378, _id=4, 
    _o=0xbfb53578) at ./kmcommands.moc:2987
#22 0x4aa44d23 in QObject::activate_signal (this=0x837d3b0, clist=0x842ce08, 
    o=0xbfb53578) at kernel/qobject.cpp:2356
#23 0x4add1360 in QSignal::signal (this=0x837d3b0, t0=@0x837d3d8)
    at .moc/debug-shared-mt/moc_qsignal.cpp:100
#24 0x4aa64d4e in QSignal::activate (this=0x837d3b0) at kernel/qsignal.cpp:212
#25 0x4aa6c7a0 in QSingleShotTimer::event (this=0x837d388)
    at kernel/qtimer.cpp:286
#26 0x4a9dc4e0 in QApplication::internalNotify (this=0xbfb53b70, 
    receiver=0x837d388, e=0xbfb538e8) at kernel/qapplication.cpp:2635
#27 0x4a9de30f in QApplication::notify (this=0xbfb53b70, receiver=0x837d388, 
    e=0xbfb538e8) at kernel/qapplication.cpp:2358
#28 0x4b0e9192 in KApplication::notify (this=0xbfb53b70, receiver=0x837d388, 
    event=0xbfb538e8)
    at /build/buildd/kdelibs-3.5.7.dfsg.1/./kdecore/kapplication.cpp:550
#29 0x4a96f595 in QApplication::sendEvent (receiver=0x837d388, 
    event=0xbfb538e8) at ../include/qapplication.h:520
#30 0x4a9cee6b in QEventLoop::activateTimers (this=0x80dd4b8)
    at kernel/qeventloop_unix.cpp:556
#31 0x4a983a10 in QEventLoop::processEvents (this=0x80dd4b8, flags=4)
    at kernel/qeventloop_x11.cpp:389
#32 0x4a9f6be6 in QEventLoop::enterLoop (this=0x80dd4b8)
    at kernel/qeventloop.cpp:198
#33 0x4a9f69f6 in QEventLoop::exec (this=0x80dd4b8)
    at kernel/qeventloop.cpp:145
#34 0x4a9de089 in QApplication::exec (this=0xbfb53b70)
    at kernel/qapplication.cpp:2758
#35 0x0804a26d in main (argc=135337096, argv=0x88f5a20)
    at /build/buildd/kdepim-3.5.7/./kmail/main.cpp:110
#36 0x45282050 in __libc_start_main () from /lib/i686/cmov/libc.so.6
#37 0x0804a001 in _start ()
Comment 1 Tommi Tervo 2007-09-20 14:42:20 UTC
*** Bug 144264 has been marked as a duplicate of this bug. ***
Comment 2 Gary Krueger 2007-10-29 15:35:21 UTC
I seem to be getting the same or a similar problem.  Up until today I was getting occasional crashes.  But now, it happens after inactivity:

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
    .    .    .
    .    .    .
    .    .    .
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208670512 (LWP 23538)]
[New Thread -1245303920 (LWP 23579)]
[New Thread -1234814064 (LWP 23578)]
[New Thread -1224324208 (LWP 23577)]
[New Thread -1213834352 (LWP 23576)]
(no debugging symbols found)
    .    .    .
    .    .    .
    .    .    .
(no debugging symbols found)
[KCrash handler]
#6  0x010d1646 in KMMsgBase::storage () from /usr/lib/libkmailprivate.so
#7  0x0110b971 in KMFolderImap::deleteMessage ()
   from /usr/lib/libkmailprivate.so
#8  0x0110c0f4 in KMFolderImap::removeMsg () from /usr/lib/libkmailprivate.so
#9  0x01058216 in KMFolder::removeMsg () from /usr/lib/libkmailprivate.so
#10 0x011af96c in KMMoveCommand::execute () from /usr/lib/libkmailprivate.so
#11 0x011a1f89 in KMCommand::slotPostTransfer ()
   from /usr/lib/libkmailprivate.so
#12 0x011a9e76 in KMCommand::qt_invoke () from /usr/lib/libkmailprivate.so
#13 0x011aa15b in KMMenuCommand::qt_invoke () from /usr/lib/libkmailprivate.so
#14 0x011aa1e7 in KMMoveCommand::qt_invoke () from /usr/lib/libkmailprivate.so
#15 0x022b316a in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#16 0x011a0bae in KMCommand::messagesTransfered ()
   from /usr/lib/libkmailprivate.so
#17 0x011a9171 in KMCommand::transferSelectedMsgs ()
   from /usr/lib/libkmailprivate.so
#18 0x011a92d7 in KMCommand::slotStart () from /usr/lib/libkmailprivate.so
#19 0x011a9e88 in KMCommand::qt_invoke () from /usr/lib/libkmailprivate.so
#20 0x011aa15b in KMMenuCommand::qt_invoke () from /usr/lib/libkmailprivate.so
#21 0x011aa1e7 in KMMoveCommand::qt_invoke () from /usr/lib/libkmailprivate.so
#22 0x022b316a in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#23 0x0264085e in QSignal::signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#24 0x022d1727 in QSignal::activate () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#25 0x022da373 in QSingleShotTimer::event ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#26 0x02249cab in QApplication::internalNotify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#27 0x0224b129 in QApplication::notify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#28 0x057e377e in KApplication::notify () from /usr/lib/libkdecore.so.4
#29 0x0223da32 in QEventLoop::activateTimers ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#30 0x021f199f in QEventLoop::processEvents ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#31 0x02263250 in QEventLoop::enterLoop ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#32 0x02263116 in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#33 0x022497bf in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#34 0x08058585 in QDialog::setGeometry ()
#35 0x008c8dec in __libc_start_main () from /lib/libc.so.6
#36 0x08057c81 in QDialog::setGeometry ()
Comment 3 Gary Krueger 2007-10-30 15:48:20 UTC
This issue goes away for me when I downgrade kdepim (kmail) to 1.9.4.
Comment 4 Thomas McGuire 2008-02-17 01:37:54 UTC

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