Bug 211431 - Kmail crash while deleting large number of messages from IMAP folder
Summary: Kmail crash while deleting large number of messages from IMAP folder
Status: RESOLVED DUPLICATE of bug 163071
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-22 13:03 UTC by Matthew Mott
Modified: 2009-10-22 14:29 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Mott 2009-10-22 13:03:07 UTC
Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.28-15-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
While deleting a large number of messages from a remote IMAP folder, KMail crashed during the operation.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  KMail::FolderJob::msgList (this=0xb0f8bb0) at /usr/include/qt4/QtCore/qatomic_i386.h:120
#7  0xb10dfc1b in KMAcctImap::ignoreJobsForMessage (this=0xa257760, msg=0xaf03ff0) at /build/buildd/kdepim-4.3.2/kmail/kmacctimap.cpp:215
#8  0xb10f7a15 in KMFolderImap::ignoreJobsForMessage (this=0xa24a728, msg=0xaf03ff0) at /build/buildd/kdepim-4.3.2/kmail/kmfolderimap.cpp:1564
#9  0xb12128ce in KMMoveCommand::execute (this=0xaf05170) at /build/buildd/kdepim-4.3.2/kmail/kmcommands.cpp:2095
#10 0xb11f6fc2 in KMCommand::slotPostTransfer (this=0xaf05170, result=KMCommand::OK) at /build/buildd/kdepim-4.3.2/kmail/kmcommands.cpp:274
#11 0xb1201444 in KMCommand::qt_metacall (this=0xaf05170, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbfabe8dc) at /build/buildd/kdepim-4.3.2/obj-i486-linux-gnu/kmail/kmcommands.moc:87
#12 0xb12146ea in KMMoveCommand::qt_metacall (this=0xaf05170, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfabe8dc) at /build/buildd/kdepim-4.3.2/obj-i486-linux-gnu/kmail/kmcommands.moc:1706
#13 0xb12147b2 in KMTrashMsgCommand::qt_metacall (this=0xaf05170, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfabe8dc) at /build/buildd/kdepim-4.3.2/obj-i486-linux-gnu/kmail/kmcommands.moc:1758
#14 0xb5c301b8 in QMetaObject::activate (sender=0xaf05170, from_signal_index=4, to_signal_index=4, argv=0xbfabe8dc) at kernel/qobject.cpp:3113
#15 0xb5c30e42 in QMetaObject::activate (sender=0xaf05170, m=0xb16305f4, local_signal_index=0, argv=0xbfabe8dc) at kernel/qobject.cpp:3187
#16 0xb11f2ed3 in KMCommand::messagesTransfered (this=0xaf05170, _t1=KMCommand::OK) at /build/buildd/kdepim-4.3.2/obj-i486-linux-gnu/kmail/kmcommands.moc:102
#17 0xb121071c in KMCommand::transferSelectedMsgs (this=0xaf05170) at /build/buildd/kdepim-4.3.2/kmail/kmcommands.cpp:368
#18 0xb1210973 in KMCommand::slotStart (this=0xaf05170) at /build/buildd/kdepim-4.3.2/kmail/kmcommands.cpp:266
#19 0xb1201453 in KMCommand::qt_metacall (this=0xaf05170, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfabead8) at /build/buildd/kdepim-4.3.2/obj-i486-linux-gnu/kmail/kmcommands.moc:86
#20 0xb12146ea in KMMoveCommand::qt_metacall (this=0xaf05170, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfabead8) at /build/buildd/kdepim-4.3.2/obj-i486-linux-gnu/kmail/kmcommands.moc:1706
#21 0xb12147b2 in KMTrashMsgCommand::qt_metacall (this=0xaf05170, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfabead8) at /build/buildd/kdepim-4.3.2/obj-i486-linux-gnu/kmail/kmcommands.moc:1758
#22 0xb5c301b8 in QMetaObject::activate (sender=0xaefd3e0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#23 0xb5c30e42 in QMetaObject::activate (sender=0xaefd3e0, m=0xb5d0c908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#24 0xb5c35f77 in QSingleShotTimer::timeout (this=0xaefd3e0) at .moc/release-shared/qtimer.moc:76
#25 0xb5c3609c in QSingleShotTimer::timerEvent (this=0xaefd3e0) at kernel/qtimer.cpp:298
#26 0xb5c2b16f in QObject::event (this=0xaefd3e0, e=0xbfabef5c) at kernel/qobject.cpp:1075
#27 0xb60ded3c in QApplicationPrivate::notify_helper (this=0x9e89560, receiver=0xaefd3e0, e=0xbfabef5c) at kernel/qapplication.cpp:4056
#28 0xb60e703e in QApplication::notify (this=0xbfabf208, receiver=0xaefd3e0, e=0xbfabef5c) at kernel/qapplication.cpp:3603
#29 0xb6cd849d in KApplication::notify (this=0xbfabf208, receiver=0xaefd3e0, event=0xbfabef5c) at /build/buildd/kde4libs-4.3.2/kdeui/kernel/kapplication.cpp:302
#30 0xb5c1abcb in QCoreApplication::notifyInternal (this=0xbfabf208, receiver=0xaefd3e0, event=0xbfabef5c) at kernel/qcoreapplication.cpp:610
#31 0xb5c49d51 in QTimerInfoList::activateTimers (this=0x9e825b4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#32 0xb5c463a0 in timerSourceDispatch (source=0x9e82580) at kernel/qeventdispatcher_glib.cpp:165
#33 0xb4cebb88 in IA__g_main_context_dispatch (context=0x9e87d90) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:1814
#34 0xb4cef0eb in g_main_context_iterate (context=0x9e87d90, block=1, dispatch=1, self=0x9e90db0) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2448
#35 0xb4cef268 in IA__g_main_context_iteration (context=0x9e87d90, may_block=1) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2511
#36 0xb5c462f8 in QEventDispatcherGlib::processEvents (this=0x9e62028, flags={i = -1079250728}) at kernel/qeventdispatcher_glib.cpp:327
#37 0xb6180a75 in QGuiEventDispatcherGlib::processEvents (this=0x9e62028, flags={i = -1079250680}) at kernel/qguieventdispatcher_glib.cpp:202
#38 0xb5c191fa in QEventLoop::processEvents (this=0xbfabf180, flags={i = -1079250616}) at kernel/qeventloop.cpp:149
#39 0xb5c19642 in QEventLoop::exec (this=0xbfabf180, flags={i = -1079250552}) at kernel/qeventloop.cpp:201
#40 0xb5c1bae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#41 0xb60debb7 in QApplication::exec () at kernel/qapplication.cpp:3525
#42 0x0804bfef in main (argc=1, argv=0xbfabf504) at /build/buildd/kdepim-4.3.2/kontact/src/main.cpp:218

This bug may be a duplicate of or related to bug 210960

Reported using DrKonqi
Comment 1 Christophe Marin 2009-10-22 14:29:59 UTC

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