Bug 195870 - Crash on multiple parallel IMAP operations
Summary: Crash on multiple parallel IMAP operations
Status: RESOLVED DUPLICATE of bug 163071
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.11.4
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-10 11:55 UTC by Malte S. Stretz
Modified: 2009-06-10 15:01 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Malte S. Stretz 2009-06-10 11:55:46 UTC
Version:           1.11.4 (using 4.2.4 (KDE 4.2.4), Kubuntu packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.28-11-generic

I thought I reported this bug already but can't find it. This bug is quite reproducible and happens often but not always (but annoys the hell out of me).

A way to trigger it is my usual mail reading behaviour
1. Go to Inbox which has a bunch of unread mails.
2. Select the first so I can skim it in the preview pane.
3. Notice I'm not interested, hit delete, mark next mail.
4. Not interested as well, hit delete again (while the old operation is still in progress).
5. Crash.
6. Restart KMail. Notice the two mails were not deleted.

The server is a Dabian sarge running Dovecot 0.99.14-1sarge0 (from backports I think).

Application: KMail (kmail), signal SIGSEGV
0x00007f5a37eb7d21 in nanosleep () from /lib/libc.so.6
Current language:  auto; currently c

Thread 1 (Thread 0x7f5a3d51f750 (LWP 4202)):
[KCrash Handler]
#5  KMail::FolderJob::msgList (this=0x27e5720) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121
#6  0x00007f5a3c148b15 in KMAcctImap::ignoreJobsForMessage (this=0xef0e10, msg=0x1028b50) at /build/buildd/kdepim-4.2.4/kmail/kmacctimap.cpp:215
#7  0x00007f5a3c270dff in KMMoveCommand::execute (this=0x25f1d00) at /build/buildd/kdepim-4.2.4/kmail/kmcommands.cpp:2096
#8  0x00007f5a3c25520b in KMCommand::slotPostTransfer (this=0x25f1d00, result=KMCommand::OK) at /build/buildd/kdepim-4.2.4/kmail/kmcommands.cpp:276
#9  0x00007f5a3c2608ce in KMCommand::qt_metacall (this=0x25f1d00, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff4556cd10)
    at /build/buildd/kdepim-4.2.4/obj-x86_64-linux-gnu/kmail/kmcommands.moc:87
#10 0x00007f5a3c272c15 in KMMoveCommand::qt_metacall (this=0x7fff4556c8c0, _c=41834272, _id=41276128, _a=0xcc3bc0) at /build/buildd/kdepim-4.2.4/obj-x86_64-linux-gnu/kmail/kmcommands.moc:1706
#11 0x00007f5a38a971f2 in QMetaObject::activate (sender=0x25f1d00, from_signal_index=<value optimized out>, to_signal_index=4, argv=0xcc3bc0) at kernel/qobject.cpp:3069
#12 0x00007f5a3c252aae in KMCommand::messagesTransfered (this=0x7fff4556c8c0, _t1=KMCommand::OK) at /build/buildd/kdepim-4.2.4/obj-x86_64-linux-gnu/kmail/kmcommands.moc:102
#13 0x00007f5a3c26f710 in KMCommand::transferSelectedMsgs (this=0x25f1d00) at /build/buildd/kdepim-4.2.4/kmail/kmcommands.cpp:370
#14 0x00007f5a3c26f956 in KMCommand::slotStart (this=0x25f1d00) at /build/buildd/kdepim-4.2.4/kmail/kmcommands.cpp:268
#15 0x00007f5a3c2608e2 in KMCommand::qt_metacall (this=0x25f1d00, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff4556cf70)
    at /build/buildd/kdepim-4.2.4/obj-x86_64-linux-gnu/kmail/kmcommands.moc:86
#16 0x00007f5a3c272c15 in KMMoveCommand::qt_metacall (this=0x7fff4556c8c0, _c=41834272, _id=41276128, _a=0xcc3bc0) at /build/buildd/kdepim-4.2.4/obj-x86_64-linux-gnu/kmail/kmcommands.moc:1706
#17 0x00007f5a38a971f2 in QMetaObject::activate (sender=0xe32970, from_signal_index=<value optimized out>, to_signal_index=4, argv=0xcc3bc0) at kernel/qobject.cpp:3069
#18 0x00007f5a38a9c52f in QSingleShotTimer::timerEvent (this=0xe32970) at kernel/qtimer.cpp:298
#19 0x00007f5a38a914d3 in QObject::event (this=0xe32970, e=0x27e5720) at kernel/qobject.cpp:1082
#20 0x00007f5a391c678d in QApplicationPrivate::notify_helper (this=0xbffd40, receiver=0xe32970, e=0x7fff4556d630) at kernel/qapplication.cpp:4084
#21 0x00007f5a391ce97a in QApplication::notify (this=0x7fff4556da90, receiver=0xe32970, e=0x7fff4556d630) at kernel/qapplication.cpp:4049
#22 0x00007f5a3cf6084b in KApplication::notify (this=0x7fff4556da90, receiver=0xe32970, event=0x7fff4556d630) at /build/buildd/kde4libs-4.2.4/kdeui/kernel/kapplication.cpp:307
#23 0x00007f5a38a8175c in QCoreApplication::notifyInternal (this=0x7fff4556da90, receiver=0xe32970, event=0x7fff4556d630) at kernel/qcoreapplication.cpp:602
#24 0x00007f5a38aae7f6 in QTimerInfoList::activateTimers (this=0xc02540) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#25 0x00007f5a38aaaf0d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:164
#26 0x00007f5a2fb7520a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0x00007f5a2fb788e0 in ?? () from /usr/lib/libglib-2.0.so.0
#28 0x00007f5a2fb78a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#29 0x00007f5a38aaae6f in QEventDispatcherGlib::processEvents (this=0xbdf0c0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323
#30 0x00007f5a3925ebef in QGuiEventDispatcherGlib::processEvents (this=0x7fff4556c8c0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#31 0x00007f5a38a80002 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 1163319456}) at kernel/qeventloop.cpp:149
#32 0x00007f5a38a803cd in QEventLoop::exec (this=0x7fff4556d8e0, flags={i = 1163319536}) at kernel/qeventloop.cpp:200
#33 0x00007f5a38a82694 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#34 0x000000000040309b in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/kdepim-4.2.4/kmail/main.cpp:146
Comment 1 Dario Andres 2009-06-10 15:01:25 UTC
Thanks

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