Bug 165540

Summary: Random crashes in slotScheduleCoSlave()
Product: [Unmaintained] kmail Reporter: Ritesh Raj Sarraf <kde-bugs>
Component: disconnected IMAPAssignee: Dirk Mueller <mueller>
Status: RESOLVED FIXED    
Severity: crash CC: amantia, bugs.kde.org3, dominik.tritscher, kitts.mailinglists, mcguire, mikolaj.mikki, moabi2000, mueller, null, vanbeek25
Priority: NOR    
Version First Reported In: 1.10.0   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: kontact.kcrash

Description Ritesh Raj Sarraf 2008-07-01 22:14:58 UTC 
Version:            (using KDE 4.0.83)
Installed from:    Debian testing/unstable Packages
OS:                Linux

Konqueror crashed for me over night. I wasn't doing anything because I was sleeping :-)
In the morning, when I looked at my laptop, kontact had crashed.
Comment 1 Ritesh Raj Sarraf 2008-07-01 22:15:48 UTC 
Application: Kontact (kontact), signal SIGSEGV
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb4d99720 (LWP 16031)]
[New Thread 0xb09dab90 (LWP 16054)]
[KCrash handler]
#6  QString::operator= (this=0xb594150, other=@0xbfdf59e8)
    at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:134
#7  0xb6ec8e1f in QUrlPrivate::parse (this=0xb594100, 
    parseOptions=QUrlPrivate::ParseAndSet) at io/qurl.cpp:220
#8  0xb6eccf80 in QUrl::host (this=0xbfdf5abc) at io/qurl.cpp:4247
#9  0xb6a440b5 in KIO::SchedulerPrivate::slotScheduleCoSlave (this=0xa17afe8)
    at /tmp/buildd/kde4libs-4.0.84/kio/kio/scheduler.cpp:884
#10 0xb6a4871e in KIO::Scheduler::qt_metacall (this=0xa15a378, 
    _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0xbfdf5ba8)
    at /tmp/buildd/kde4libs-4.0.84/obj-i486-linux-gnu/kio/scheduler.moc:105
#11 0xb6f26090 in QMetaObject::activate (sender=0xa17b004, 
    from_signal_index=4, to_signal_index=4, argv=0x0)
    at kernel/qobject.cpp:3010
#12 0xb6f26e12 in QMetaObject::activate (sender=0xa17b004, m=0xb6ff3ae4, 
    local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3080
#13 0xb6f60f07 in QTimer::timeout (this=0xa17b004)
    at .moc/release-shared/moc_qtimer.cpp:126
#14 0xb6f2cabe in QTimer::timerEvent (this=0xa17b004, e=0xbfdf604c)
    at kernel/qtimer.cpp:263
#15 0xb6f20b7f in QObject::event (this=0xa17b004, e=0xbfdf604c)
    at kernel/qobject.cpp:1105
#16 0xb734766c in QApplicationPrivate::notify_helper (this=0x9d05888, 
    receiver=0xa17b004, e=0xbfdf604c) at kernel/qapplication.cpp:3772
#17 0xb734f43e in QApplication::notify (this=0xbfdf767c, receiver=0xa17b004, 
    e=0xbfdf604c) at kernel/qapplication.cpp:3366
#18 0xb7cd3c8d in KApplication::notify (this=0xbfdf767c, receiver=0xa17b004, 
    event=0xbfdf604c)
    at /tmp/buildd/kde4libs-4.0.84/kdeui/kernel/kapplication.cpp:311
#19 0xb6f11541 in QCoreApplication::notifyInternal (this=0xbfdf767c, 
    receiver=0xa17b004, event=0xbfdf604c) at kernel/qcoreapplication.cpp:587
#20 0xb6f3f5b1 in QTimerInfoList::activateTimers (this=0x9d08614)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#21 0xb6f3bbf0 in timerSourceDispatch (source=0x9d085e0)
    at kernel/qeventdispatcher_glib.cpp:166
#22 0xb5751978 in IA__g_main_context_dispatch (context=0x9d07a98)
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c:2009
#23 0xb5754bce in g_main_context_iterate (context=0x9d07a98, block=1, 
    dispatch=1, self=0x9d05a08)
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c:2642
#24 0xb575511c in IA__g_main_context_iteration (context=0x9d07a98, 
    may_block=1) at /build/buildd/glib2.0-2.16.3/glib/gmain.c:2705
#25 0xb6f3bb48 in QEventDispatcherGlib::processEvents (this=0x9d05850, flags=
      {i = -1075879496}) at kernel/qeventdispatcher_glib.cpp:325
#26 0xb73e0415 in QGuiEventDispatcherGlib::processEvents (this=0x9d05850, 
    flags={i = -1075879448}) at kernel/qguieventdispatcher_glib.cpp:204
#27 0xb6f0fc2a in QEventLoop::processEvents (this=0xbfdf625c, flags=
      {i = -1075879384}) at kernel/qeventloop.cpp:149
#28 0xb6f0fdea in QEventLoop::exec (this=0xbfdf625c, flags={i = -1075879324})
    at kernel/qeventloop.cpp:200
#29 0xb77a92f7 in QDialog::exec (this=0xa0f4d38) at dialogs/qdialog.cpp:453
#30 0xb7c4b7d4 in KMessageBox::createKMessageBox (dialog=0xa0f4d38, 
    icon=@0xbfdf64a8, text=@0xbfdf66a0, strlist=@0xbfdf659c, ask=@0xbfdf64fc, 
    checkboxReturn=0xbfdf651b, options={i = -1075878748}, 
    details=@0xbfdf64f4, notifyType=QMessageBox::Information)
    at /tmp/buildd/kde4libs-4.0.84/kdeui/dialogs/kmessagebox.cpp:303
#31 0xb7c4c761 in KMessageBox::createKMessageBox (dialog=0xa0f4d38, 
    icon=QMessageBox::Information, text=@0xbfdf66a0, strlist=@0xbfdf659c, 
    ask=@0xbfdf64fc, checkboxReturn=0xbfdf651b, options={i = -1075878664}, 
    details=@0xbfdf64f4)
    at /tmp/buildd/kde4libs-4.0.84/kdeui/dialogs/kmessagebox.cpp:154
#32 0xb7c4edaf in KMessageBox::informationListWId (parent_id=73400321, 
    text=@0xbfdf66a0, strlist=@0xbfdf659c, caption=@0xbfdf6690, 
    dontShowAgainName=@0xbfdf6684, options={i = -1075878560})
    at /tmp/buildd/kde4libs-4.0.84/kdeui/dialogs/kmessagebox.cpp:1000
#33 0xb7c4ef48 in KMessageBox::informationList (parent=0x9d49678, 
    text=@0xbfdf66a0, strlist=@0xbfdf659c, caption=@0xbfdf6690, 
    dontShowAgainName=@0xbfdf6684, options={i = -1075878504})
    at /tmp/buildd/kde4libs-4.0.84/kdeui/dialogs/kmessagebox.cpp:967
#34 0xb7c4efa8 in KMessageBox::information (parent=0x9d49678, 
    text=@0xbfdf66a0, caption=@0xbfdf6690, dontShowAgainName=@0xbfdf6684, 
    options={i = -1075878272})
    at /tmp/buildd/kde4libs-4.0.84/kdeui/dialogs/kmessagebox.cpp:954
#35 0xb1605543 in KMail::ImapAccountBase::handleError (this=0xa29fe98, 
    errorCode=149, errorMsg=@0xbfdf6758, job=0xaa24960, context=@0xbfdf67e4, 
    abortSync=false)
    at /tmp/buildd/kdepim-4.0.84/kmail/imapaccountbase.cpp:1034
#36 0xb15fabb3 in KMail::ImapAccountBase::handleJobError (this=0xa29fe98, 
    job=0xaa24960, context=@0xbfdf67e4, abortSync=false)
    at /tmp/buildd/kdepim-4.0.84/kmail/imapaccountbase.cpp:367
#37 0xb15fbc10 in KMail::ImapAccountBase::slotSimpleResult (this=0xa29fe98, 
    job=0xaa24960) at /tmp/buildd/kdepim-4.0.84/kmail/imapaccountbase.cpp:921
#38 0xb160663b in KMail::ImapAccountBase::qt_metacall (this=0xa29fe98, 
    _c=QMetaObject::InvokeMetaMethod, _id=20, _a=0xbfdf691c)
    at /tmp/buildd/kdepim-4.0.84/obj-i486-linux-gnu/kmail/imapaccountbase.moc:137
#39 0xb160f4da in KMAcctCachedImap::qt_metacall (this=0xa29fe98, 
    _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbfdf691c)
    at /tmp/buildd/kdepim-4.0.84/obj-i486-linux-gnu/kmail/kmacctcachedimap.moc:77
#40 0xb6f26090 in QMetaObject::activate (sender=0xaa24960, 
    from_signal_index=7, to_signal_index=7, argv=0xbfdf691c)
    at kernel/qobject.cpp:3010
#41 0xb6f26e12 in QMetaObject::activate (sender=0xaa24960, m=0xb7207888, 
    local_signal_index=3, argv=0xbfdf691c) at kernel/qobject.cpp:3080
#42 0xb70d0c33 in KJob::result (this=0xaa24960, _t1=0xaa24960)
    at /tmp/buildd/kde4libs-4.0.84/obj-i486-linux-gnu/kdecore/kjob.moc:186
#43 0xb70d1142 in KJob::emitResult (this=0xaa24960)
    at /tmp/buildd/kde4libs-4.0.84/kdecore/jobs/kjob.cpp:290
#44 0xb6999b9f in KIO::SimpleJob::slotFinished (this=0xaa24960)
    at /tmp/buildd/kde4libs-4.0.84/kio/kio/job.cpp:496
#45 0xb6998183 in KIO::SimpleJob::slotError (this=0xaa24960, err=149, 
    errorText=@0xbfdf6c30) at /tmp/buildd/kde4libs-4.0.84/kio/kio/job.cpp:508
#46 0xb699837b in KIO::SimpleJob::qt_metacall (this=0xaa24960, 
    _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfdf6ae8)
    at /tmp/buildd/kde4libs-4.0.84/obj-i486-linux-gnu/kio/jobclasses.moc:155
#47 0xb6f26090 in QMetaObject::activate (sender=0xa8ad598, 
    from_signal_index=6, to_signal_index=6, argv=0xbfdf6ae8)
    at kernel/qobject.cpp:3010
#48 0xb6f26e12 in QMetaObject::activate (sender=0xa8ad598, m=0xb6b48664, 
    local_signal_index=2, argv=0xbfdf6ae8) at kernel/qobject.cpp:3080
#49 0xb6a5d6f9 in KIO::SlaveInterface::error (this=0xa8ad598, _t1=149, 
    _t2=@0xbfdf6c30)
    at /tmp/buildd/kde4libs-4.0.84/obj-i486-linux-gnu/kio/slaveinterface.moc:149
#50 0xb6a613e7 in KIO::SlaveInterface::dispatch (this=0xa8ad598, _cmd=102, 
    rawdata=@0xbfdf6c74)
    at /tmp/buildd/kde4libs-4.0.84/kio/kio/slaveinterface.cpp:212
#51 0xb6a5dde7 in KIO::SlaveInterface::dispatch (this=0xa8ad598)
    at /tmp/buildd/kde4libs-4.0.84/kio/kio/slaveinterface.cpp:90
#52 0xb6a4dddd in KIO::Slave::gotInput (this=0xa8ad598)
    at /tmp/buildd/kde4libs-4.0.84/kio/kio/slave.cpp:319
#53 0xb6a50823 in KIO::Slave::qt_metacall (this=0xa8ad598, 
    _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfdf6d88)
    at /tmp/buildd/kde4libs-4.0.84/obj-i486-linux-gnu/kio/slave.moc:75
#54 0xb6f26090 in QMetaObject::activate (sender=0xa8c8640, 
    from_signal_index=4, to_signal_index=4, argv=0x0)
    at kernel/qobject.cpp:3010
#55 0xb6f26e12 in QMetaObject::activate (sender=0xa8c8640, m=0xb6b452c0, 
    local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3080
#56 0xb6960487 in KIO::Connection::readyRead (this=0xa8c8640)
    at /tmp/buildd/kde4libs-4.0.84/obj-i486-linux-gnu/kio/connection.moc:84
#57 0xb6962549 in KIO::ConnectionPrivate::dequeue (this=0xa8c8670)
    at /tmp/buildd/kde4libs-4.0.84/kio/kio/connection.cpp:82
#58 0xb69626d6 in KIO::Connection::qt_metacall (this=0xa8c8640, 
    _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xab4ae78)
    at /tmp/buildd/kde4libs-4.0.84/obj-i486-linux-gnu/kio/connection.moc:72
#59 0xb6f1f20b in QMetaCallEvent::placeMetaCall (this=0xa3f61b0, 
    object=0xa8c8640) at kernel/qobject.cpp:535
#60 0xb6f20dc9 in QObject::event (this=0xa8c8640, e=0xa3f61b0)
    at kernel/qobject.cpp:1140
#61 0xb734766c in QApplicationPrivate::notify_helper (this=0x9d05888, 
    receiver=0xa8c8640, e=0xa3f61b0) at kernel/qapplication.cpp:3772
#62 0xb734f43e in QApplication::notify (this=0xbfdf767c, receiver=0xa8c8640, 
    e=0xa3f61b0) at kernel/qapplication.cpp:3366
#63 0xb7cd3c8d in KApplication::notify (this=0xbfdf767c, receiver=0xa8c8640, 
    event=0xa3f61b0)
    at /tmp/buildd/kde4libs-4.0.84/kdeui/kernel/kapplication.cpp:311
#64 0xb6f11541 in QCoreApplication::notifyInternal (this=0xbfdf767c, 
    receiver=0xa8c8640, event=0xa3f61b0) at kernel/qcoreapplication.cpp:587
#65 0xb6f121b5 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, 
    event_type=0, data=0x9cf5450)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#66 0xb6f123cd in QCoreApplication::sendPostedEvents (receiver=0x0, 
    event_type=0) at kernel/qcoreapplication.cpp:1091
#67 0xb6f3beff in postEventSourceDispatch (s=0x9d07b20)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#68 0xb5751978 in IA__g_main_context_dispatch (context=0x9d07a98)
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c:2009
#69 0xb5754bce in g_main_context_iterate (context=0x9d07a98, block=1, 
    dispatch=1, self=0x9d05a08)
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c:2642
#70 0xb575511c in IA__g_main_context_iteration (context=0x9d07a98, 
    may_block=1) at /build/buildd/glib2.0-2.16.3/glib/gmain.c:2705
#71 0xb6f3bb48 in QEventDispatcherGlib::processEvents (this=0x9d05850, flags=
      {i = -1075874744}) at kernel/qeventdispatcher_glib.cpp:325
#72 0xb73e0415 in QGuiEventDispatcherGlib::processEvents (this=0x9d05850, 
    flags={i = -1075874696}) at kernel/qguieventdispatcher_glib.cpp:204
#73 0xb6f0fc2a in QEventLoop::processEvents (this=0xbfdf74f0, flags=
      {i = -1075874632}) at kernel/qeventloop.cpp:149
#74 0xb6f0fdea in QEventLoop::exec (this=0xbfdf74f0, flags={i = -1075874568})
    at kernel/qeventloop.cpp:200
#75 0xb6f12495 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#76 0xb73474e7 in QApplication::exec () at kernel/qapplication.cpp:3304
#77 0x0804bd9e in main (argc=1, argv=0xbfdf7874)
    at /tmp/buildd/kdepim-4.0.84/kontact/src/main.cpp:210
#78 0xb6ba6450 in __libc_start_main () from /lib/i686/cmov/libc.so.6
#79 0x0804a511 in _start ()
#0  0xb7fdd424 in __kernel_vsyscall ()
Comment 2 Will Stephenson 2008-07-18 19:18:59 UTC 
*** Bug 166915 has been marked as a duplicate of this bug. ***
Comment 3 Thomas McGuire 2008-07-19 16:43:55 UTC 
*** Bug 167005 has been marked as a duplicate of this bug. ***
Comment 4 Thomas McGuire 2008-07-19 18:44:21 UTC 
*** Bug 166915 has been marked as a duplicate of this bug. ***
Comment 5 Christophe Marin 2008-07-25 12:29:01 UTC 
*** Bug 167416 has been marked as a duplicate of this bug. ***
Comment 6 Christophe Marin 2008-07-27 10:04:18 UTC 
*** Bug 167511 has been marked as a duplicate of this bug. ***
Comment 7 Thomas McGuire 2008-07-27 17:02:13 UTC 
Sorry, I can't reproduce this problem, I need more data on how to reproduce it.

@mstarkey: Are you sure it was a POP3 problem? Maybe a IMAP connection was open in the background?
Comment 8 Kishore 2008-07-27 17:54:18 UTC 
On Sunday 27 Jul 2008 8:32:14 pm Thomas McGuire wrote:
> Sorry, I can't reproduce this problem, I need more data on how to reproduce
> it.
>
>  mstarkey: Are you sure it was a POP3 problem? Maybe a IMAP connection was
> open in the background?


I do not have any POP accounts setup and yet i face these crashes so i doubt 
it is POP related. However, i have almost always faced this when i have some 
network errors.

Previously, i used to get a dialog that tells me that there was connection 
error. The moment i click on OK, kontact crashes. In recent builds i do not 
get that error message but directly the crash.

As far as i can recall, when i used to get those error messages kontact would 
crash if it were minimized to system tray but not if the window was open. I 
could be wrong here though.
Comment 9 Thomas McGuire 2008-07-27 19:33:08 UTC 
> I do not have any POP accounts setup and yet i face these crashes so i doubt it is POP related. 
I think this is only IMAP related, too, but one reporter said he had the problem with POP, that's why I asked.

>i have almost always faced this when i have some network errors. 
Well, the thing is I tried to simulate this, by doing "ifdown eth0" during syncing my disconnected IMAP folder, for example. No error here, the syncing just stopped at the current progress step. I also tried deleting the IMAP slave with "killall -9 kio_imap4", which just showed an error message, but no crash.
Minimizing to the system tray also didn't make a difference to me.
Comment 10 Kishore 2008-07-28 20:02:17 UTC 
I had this crash again today and it seems to be a somewhat saner backtrace 
than i had before. I hope it is useful.

One thing to note if it matters (I read about the abort() bug) is that i am 
not using qt-copy but qt 4.4 packages supplied for Kubuntu Hardy.


Created an attachment (id=26461)
kontact.kcrash
Comment 11 Jakub Schmidtke 2008-07-29 11:53:48 UTC 
I'm experiencing the same error.
Every night if I leave my system on, next morning there is crash
notification from kmail waiting for me ;)
My backtrace is from release version, so doesn't make much sense, but it ends with KIO::SchedulerPrivate::slotScheduleCoSlave as well.
I have some POP3 accounts, and some "disconnected IMAP" accounts, no "normal" IMAP accounts.
Comment 12 Thomas McGuire 2008-07-29 13:02:34 UTC 
More backtraces unfortunately don't help, I need a way to trigger this myself in order to be able to fix the bug.

>One thing to note if it matters (I read about the abort() bug) is that i am  not using qt-copy but qt 4.4 packages supplied for Kubuntu Hardy. 

No, completely unrelated I think.
Comment 13 Dirk Mueller 2008-07-29 13:34:09 UTC 
I think I've found the fix now, and I'm testing it for a few more hours.
Comment 14 Kishore 2008-07-30 17:17:18 UTC 
@Dirk, Perhaps if you post the patch in here some of us could help with the testing?
Comment 15 Thomas McGuire 2008-07-31 23:27:29 UTC 
*** Bug 167889 has been marked as a duplicate of this bug. ***
Comment 16 Mikolaj Mackowiak 2008-08-01 10:44:14 UTC 
If this might help, I noticed, that kmail crashes often after resuming from hibernation.
Comment 17 Dominik Tritscher 2008-08-04 17:12:27 UTC 
*** Bug 168311 has been marked as a duplicate of this bug. ***
Comment 18 Christophe Marin 2008-08-04 17:55:28 UTC 
*** Bug 168288 has been marked as a duplicate of this bug. ***
Comment 19 Bram Schoenmakers 2008-08-16 13:07:45 UTC 
*** Bug 169219 has been marked as a duplicate of this bug. ***
Comment 20 Dirk Mueller 2008-08-20 05:13:35 UTC 
fixed for KDE 4.4.1 (r849755)
Comment 21 Mikolaj Mackowiak 2008-08-25 11:43:53 UTC 
Fixed? I don't think so...
I have Kmail 1.10 KDE 4.4.1 "release 38.1"
and kmail crashed afer I resumed from hibernation and connected to wireles network. then I clicked check mail button, Kmail was checking namespace (on gmail imap account) and bang! crashed. Just like before.

Program: KMail (kmail), sygnał SIGSEGV
[?1034h(no debugging symbols found)
(no debugging symbols found)
[...]
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fd3276bb700 (LWP 22588)]
[New Thread 0x41c8e950 (LWP 23622)]
(no debugging symbols found)
[...]
(no debugging symbols found)
[KCrash handler]
#5  0x00007fd31fe3c130 in QUrl::QUrl () from /usr/lib64/libQtCore.so.4
#6  0x00007fd321202629 in KUrl::KUrl () from /usr/lib64/libkdecore.so.5
#7  0x00007fd3220898ff in ?? () from /usr/lib64/libkio.so.5
#8  0x00007fd32208cb54 in KIO::Scheduler::qt_metacall ()
   from /usr/lib64/libkio.so.5
#9  0x00007fd31fe8f4e0 in QMetaObject::activate ()
   from /usr/lib64/libQtCore.so.4
#10 0x00007fd31fe8b6e3 in QObject::event () from /usr/lib64/libQtCore.so.4
#11 0x00007fd31c9e492d in QApplicationPrivate::notify_helper ()
   from /usr/lib64/libQtGui.so.4
#12 0x00007fd31c9eacfa in QApplication::notify () from /usr/lib64/libQtGui.so.4
#13 0x00007fd321b69ddb in KApplication::notify () from /usr/lib64/libkdeui.so.5
#14 0x00007fd31fe7de9c in QCoreApplication::notifyInternal ()
   from /usr/lib64/libQtCore.so.4
#15 0x00007fd31fea43c6 in ?? () from /usr/lib64/libQtCore.so.4
#16 0x00007fd31fea4678 in QEventDispatcherUNIX::processEvents ()
   from /usr/lib64/libQtCore.so.4
#17 0x00007fd31ca6534a in ?? () from /usr/lib64/libQtGui.so.4
#18 0x00007fd31fe7c7f2 in QEventLoop::processEvents ()
   from /usr/lib64/libQtCore.so.4
#19 0x00007fd31fe7c985 in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#20 0x00007fd31fe7ea25 in QCoreApplication::exec ()
   from /usr/lib64/libQtCore.so.4
#21 0x000000000040309b in _start ()
#0  0x00007fd31b397261 in nanosleep () from /lib64/libc.so.6
Comment 22 Thomas McGuire 2008-09-11 22:03:45 UTC 
*** Bug 164496 has been marked as a duplicate of this bug. ***