Summary: | assertion !transferInProgress( serNum ) failed | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Oliver Putz <Regnaron> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | andreaswuest, echidnaman, envite, finex, franke.daniel, gokcen.eraslan, kde-bugs, klaus.layer+kde, lure, marcus, martin.fitzpatrick, moabi2000, mueller, thiago, usenbinz |
Priority: | NOR | ||
Version: | SVN trunk (KDE 4) | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | All | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | kontact-crash.txt |
Description
Oliver Putz
2008-01-30 22:59:44 UTC
Same backtrace as in bug 156293. Before posting crash reports, please check if you've already reported a bug with the same backtrace. *** This bug has been marked as a duplicate of 156293 *** Hmm, I think this one is a different bug after all. Still valid in a current SVN version Still valid in a current SVN version, also on Windows. *** Bug 166024 has been marked as a duplicate of this bug. *** *** Bug 169471 has been marked as a duplicate of this bug. *** I can confirm this crash, happens quite frequently *** Bug 174816 has been marked as a duplicate of this bug. *** *** Bug 176571 has been marked as a duplicate of this bug. *** *** Bug 176690 has been marked as a duplicate of this bug. *** I get this crash at least couple of times per day if I use Disconnected IMAP. Did not see this when using regular IMAP (on same MS Exchange 2003 IMAP server). I am running up-to-date KDE 4.2 from SVN. Is there anything I can do to help fix this problem? Created attachment 29924 [details]
kontact-crash.txt
With recent SVN, I get a bit less of crashes (one per week), but I still get some.
Mostly it looks like it is related with large operations.
Last crash (today) happened when I did "Move all messages to Trash" on my Junk Mail folder.
After restart, Junk mail folder was empty (local dimap cache), but was filled with all e-mails after sync with IMAP server (MS Exchange 2003).
*** Bug 179632 has been marked as a duplicate of this bug. *** Same backtrace here (v4.1.4) when closing Kontact during send operation (disconnected IMAP). Addition to comment #14: I never got this crash with 4.1.2 or 4.1.3, but since the first crash yesterday on 4.1.4, I get this quite regularly now. Even if the machine is unattended and kmail is only supposed to check for mail every now and then. Argh! *** Bug 182649 has been marked as a duplicate of this bug. *** I'm not able to reproduce it: on step 3 (Save mail in Draft folder on the IMAP) the mail il saved and no password are asked. Kmail is still running and there is no crash. Cannot reproduce on KDE 4.2.2 (Kubuntu). As for FiNeX saving to the IMAP Draft folder does not ask for password, saves normally, no crash. Thanks for double checking Martin. We have received a report about this crash at https://launchpad.net/bugs/378232 in regards to KDE 4.2.3. Steps to reproduce are: * write a mail with an attachement that is greater than approx 1MB, just to ensure the sending process needs some time. * click on send, the mail comes into the outbox, kmail/kontact starts sending. * close Kontact WHILE sending the mail. Anwendung: Kontact (kontact), Signal SIGABRT [Current thread is 0 (LWP 4242)] Thread 2 (Thread 0xab4a2b90 (LWP 4277)): #0 0xb80ca430 in __kernel_vsyscall () #1 0xb5a567b1 in select () from /lib/tls/i686/cmov/libc.so.6 #2 0xb5d213d0 in QProcessManager::run (this=0x9ab2de8) at io/qprocess_unix.cpp:305 #3 0xb5c4f56e in QThreadPrivate::start (arg=0x9ab2de8) at thread/qthread_unix.cpp:189 #4 0xb52544ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #5 0xb5a5e49e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb49709c0 (LWP 4242)): [KCrash Handler] #6 0xb80ca430 in __kernel_vsyscall () #7 0xb59a56d0 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0xb59a7098 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0xb5c471e5 in qt_message_output (msgType=QtFatalMsg, buf=0x9fcdd48 "ASSERT: \"!transferInProgress( serNum )\" in file /build/buildd/kdepim-4.2.3/kmail/messageproperty.cpp, line 180") at global/qglobal.cpp:2017 #10 0xb5c472d1 in qFatal (msg=0xb5d960d8 "ASSERT: \"%s\" in file %s, line %d") at global/qglobal.cpp:2216 #11 0xb5c473c5 in qt_assert (assertion=0xb1442c6b "!transferInProgress( serNum )", file=0xb1442c18 "/build/buildd/kdepim-4.2.3/kmail/messageproperty.cpp", line=180) at global/qglobal.cpp:1786 #12 0xb0f73cf0 in KMail::MessageProperty::forget (msgBase=0xab08ba8) at /build/buildd/kdepim-4.2.3/kmail/messageproperty.cpp:180 #13 0xb0fd87da in ~KMMsgBase (this=0xab08ba8) at /build/buildd/kdepim-4.2.3/kmail/kmmsgbase.cpp:125 #14 0xb0e37624 in ~KMMessage (this=0xab08ba8) at /build/buildd/kdepim-4.2.3/kmail/kmmessage.cpp:225 #15 0xb0fe1919 in KMMsgList::clear (this=0x9f37c70, doDelete=true, syncDict=false) at /build/buildd/kdepim-4.2.3/kmail/kmmsglist.cpp:37 #16 0xb105741f in KMFolderMaildir::reallyDoClose (this=0x9f37c20) at /build/buildd/kdepim-4.2.3/kmail/kmfoldermaildir.cpp:203 #17 0xb0f60f7d in FolderStorage::close (this=0x6, aForced=146) at /build/buildd/kdepim-4.2.3/kmail/folderstorage.cpp:110 #18 0xb0f2ed06 in KMFolder::close (this=0x9f29538, owner=0xb145d142 "kmkernel", force=<value optimized out>) at /build/buildd/kdepim-4.2.3/kmail/kmfolder.cpp:542 #19 0xb1073803 in KMKernel::cleanup (this=0x9e96840) at /build/buildd/kdepim-4.2.3/kmail/kmkernel.cpp:1678 #20 0xb15d783b in ~KMailPart (this=0x9e43950) at /build/buildd/kdepim-4.2.3/kmail/kmail_part.cpp:141 #21 0xb79660e9 in ~Plugin (this=0x9e1c1b0, __vtt_parm=0x1092) at /build/buildd/kdepim-4.2.3/kontactinterfaces/plugin.cpp:86 #22 0xb1a0776c in ~KMailPlugin (this=0x9e1c1b0) at /build/buildd/kdepim-4.2.3/kontact/plugins/kmail/kmail_plugin.cpp:150 #23 0xb7980fce in ~MainWindow (this=0x9b6bad0) at /build/buildd/kdepim-4.2.3/kontact/src/mainwindow.cpp:271 #24 0xb5d528d5 in qDeleteInEventHandler (o=0x6) at kernel/qobject.cpp:3822 #25 0xb5d5417b in QObject::event (this=0x9b6bad0, e=0xabba6f8) at kernel/qobject.cpp:1101 #26 0xb624b1c0 in QWidget::event (this=0x9b6bad0, event=0xabba6f8) at kernel/qwidget.cpp:7918 #27 0xb6646a07 in QMainWindow::event (this=0x9b6bad0, event=0xabba6f8) at widgets/qmainwindow.cpp:1402 #28 0xb6ef9a67 in KMainWindow::event (this=0x9b6bad0, ev=0xabba6f8) at /build/buildd/kde4libs-4.2.3/kdeui/widgets/kmainwindow.cpp:1094 #29 0xb6f3e84c in KXmlGuiWindow::event (this=0x9b6bad0, ev=0xabba6f8) at /build/buildd/kde4libs-4.2.3/kdeui/xmlgui/kxmlguiwindow.cpp:131 #30 0xb61f4bcc in QApplicationPrivate::notify_helper (this=0x9ab8330, receiver=0x9b6bad0, e=0xabba6f8) at kernel/qapplication.cpp:4057 #31 0xb61fcfc2 in QApplication::notify (this=0xbfde72a8, receiver=0x9b6bad0, e=0xabba6f8) at kernel/qapplication.cpp:4022 #32 0xb6e15e5d in KApplication::notify (this=0xbfde72a8, receiver=0x9b6bad0, event=0xabba6f8) at /build/buildd/kde4libs-4.2.3/kdeui/kernel/kapplication.cpp:307 #33 0xb5d437ab in QCoreApplication::notifyInternal (this=0xbfde72a8, receiver=0x9b6bad0, event=0xabba6f8) at kernel/qcoreapplication.cpp:610 #34 0xb5d44405 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9a93428) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #35 0xb5d445fd in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140 #36 0xb5d6f58f in postEventSourceDispatch (s=0x9ab9ed8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #37 0xb4e26b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #38 0xb4e2a0eb in ?? () from /usr/lib/libglib-2.0.so.0 #39 0xb4e2a268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #40 0xb5d6f1d8 in QEventDispatcherGlib::processEvents (this=0x9a981b8, flags={i = -1075941000}) at kernel/qeventdispatcher_glib.cpp:324 #41 0xb6296765 in QGuiEventDispatcherGlib::processEvents (this=0x9a981b8, flags={i = -1075940952}) at kernel/qguieventdispatcher_glib.cpp:202 #42 0xb5d41dda in QEventLoop::processEvents (this=0xbfde7220, flags={i = -1075940888}) at kernel/qeventloop.cpp:149 #43 0xb5d4221a in QEventLoop::exec (this=0xbfde7220, flags={i = -1075940824}) at kernel/qeventloop.cpp:200 #44 0xb5d446c9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #45 0xb61f4a47 in QApplication::exec () at kernel/qapplication.cpp:3526 #46 0x0804c072 in main (argc=1, argv=0xbfde75a4) at /build/buildd/kdepim-4.2.3/kontact/src/main.cpp:218 Oh, and it should be pointed out that in the downstream bug, the reporter said that this only happens with kontact + kmail, and not kmail on its own. Can you ask the reporter if he's using Qt 4.5? I think it's abug already fixed there. The repository containing the KDE 4.2 packages also contains Qt 4.5.1 packages, so it is pretty safe to say that he is using Qt 4.5.1 since an upgrade with those repos available would upgrade both Qt and KDE. *** Bug 197241 has been marked as a duplicate of this bug. *** *** Bug 196930 has been marked as a duplicate of this bug. *** I can still reproduce the bug with KDE 4.3.4 and Qt4.5.3. 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 |