Summary: | KMail crashes after sending outgoing message [KMMessage::transferInProgress, FolderStorage::canAddMsgNow, KMFolderMaildir::addMsg] | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Wim Delvaux <wim.delvaux> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | alinm.elena, andresbajotierra, bjoern, EssL.main, joanjerezt, kollix, ochach, rafal, zhanghan |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Wim Delvaux
2009-07-27 22:07:42 UTC
Can confirm with trunk: Reproducible with the following: send a larger mail, which takes some seconds to upload. During upload, double click the mail in the outbox folder to have it open in a composer window. Wait until the upload has finished, then close the composer window -> crash: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 0x00000000 in ?? () #7 0xb763ebcc in FolderStorage::canAddMsgNow (this=0x81cef30, aMsg=0x87532e0, aIndex_ret=0x0) at /home/KDE4/source/kdepim/kmail/folderstorage.cpp:308 #8 0xb7700808 in KMFolderMaildir::addMsg (this=0x81cef30, aMsg=0x87532e0, index_return=0x0) at /home/KDE4/source/kdepim/kmail/kmfoldermaildir.cpp:333 #9 0xb7615065 in KMFolder::addMsg (this=0x81cec40, msg=0x87532e0, index_return=0x0) at /home/KDE4/source/kdepim/kmail/kmfolder.cpp:440 #10 0xb75f8ff5 in ~KMComposeWin (this=0x87637e0) at /home/KDE4/source/kdepim/kmail/kmcomposewin.cpp:404 #11 0xb6cc00d5 in qDeleteInEventHandler(QObject*) () from /usr/lib/libQtCore.so.4 #12 0xb6cc199b in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #13 0xb61dccd0 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4 #14 0xb658c1b7 in QMainWindow::event(QEvent*) () from /usr/lib/libQtGui.so.4 #15 0xb7fd027f in KMainWindow::event (this=0x87637e0, ev=0x8a953e8) at /media/disk/KDE4/source/kdelibs/kdeui/widgets/kmainwindow.cpp:1094 #16 0xb800f61c in KXmlGuiWindow::event (this=0x87637e0, ev=0x8a953e8) at /media/disk/KDE4/source/kdelibs/kdeui/xmlgui/kxmlguiwindow.cpp:131 #17 0xb61867fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #18 0xb618ebd2 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #19 0xb7ef90b1 in KApplication::notify (this=0xbf845c38, receiver=0x87637e0, event=0x8a953e8) at /media/disk/KDE4/source/kdelibs/kdeui/kernel/kapplication.cpp:302 #20 0xb6cb116b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #21 0xb6cb1db5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #22 0xb6cb1fad in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4 #23 0xb6cdcc8f in ?? () from /usr/lib/libQtCore.so.4 #24 0xb43cc9c8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #25 0xb43d0083 in ?? () from /usr/lib/libglib-2.0.so.0 #26 0xb43d0241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #27 0xb6cdc8d8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #28 0xb6226cc5 in ?? () from /usr/lib/libQtGui.so.4 #29 0xb6caf78a in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #30 0xb6cafbd2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #31 0xb6cb2079 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #32 0xb6186677 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #33 0x0804ab1a in main (argc=-1217418240, argv=0xb76fac90) at /home/KDE4/source/kdepim/kmail/main.cpp:146 *** Bug 203408 has been marked as a duplicate of this bug. *** I have a bit (one-step) more exact backtrace it seems: #5 0x00000000031b9ec0 in ?? () #6 0x00007f0e7c72312d in KMMessage::transferInProgress (this=0x38c3c80) at ../../kmail/kmmessage.cpp:270 #7 0x00007f0e7c82ad55 in FolderStorage::canAddMsgNow (this=0x17bff10, aMsg=0x38c3c80, aIndex_ret=0x0) at ../../kmail/folderstorage.cpp:308 #8 0x00007f0e7c904fb5 in KMFolderMaildir::addMsg (this=0x38c3c80, aMsg=0x38c3c80, index_return=0x0) at ../../kmail/kmfoldermaildir.cpp:333 Any idea how to resolve that #5 0x00000000031b9ec0 in ?? part? *** This bug has been marked as a duplicate of bug 181611 *** *** Bug 257715 has been marked as a duplicate of this bug. *** [Comment from a bug triager] From bug 261137: -- Information about the crash: Kmail crashes when i send a mail. Before the mail transfering complete, I click and view the mail still in the outbox.But meanwhile the transfering completed, and Kmail crashed. - Updated backtrace: [KCrash Handler] #6 0x00007fcd0fdbad87 in KMMessage::transferInProgress (this=0x209c0b0) at /usr/src/debug/kdepim-4.4.8/kmail/kmmessage.cpp:271 #7 0x00007fcd0fe909f5 in FolderStorage::canAddMsgNow (this=0x92ca00, aMsg=0x209c0b0, aIndex_ret=<value optimized out>) at /usr/src/debug/kdepim-4.4.8/kmail/folderstorage.cpp:311 #8 0x00007fcd0ff567c5 in KMFolderMaildir::addMsg (this=0x92ca00, aMsg=0x209c0b0, index_return=0x0) at /usr/src/debug/kdepim-4.4.8/kmail/kmfoldermaildir.cpp:322 #9 0x00007fcd0fe4e98f in KMComposeWin::~KMComposeWin (this=0x3318420, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /usr/src/debug/kdepim-4.4.8/kmail/kmcomposewin.cpp:407 #10 0x00007fcd0fe4f129 in KMComposeWin::~KMComposeWin (this=0x3318420, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /usr/src/debug/kdepim-4.4.8/kmail/kmcomposewin.cpp:432 ... *** Bug 261137 has been marked as a duplicate of this bug. *** Created attachment 56803 [details]
New crash information added by DrKonqi
Opened an email in outbox after I already pressed send (to check again what I was sending) by double clicking (opened different window), after I closed it kontact krashed.
*** Bug 279375 has been marked as a duplicate of this bug. *** Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding |