Bug 122055 - KMail hangs after clicking "cancel" on a "fetching-mail"-job (imap) (deadlock) (gbd backtrace)
Summary: KMail hangs after clicking "cancel" on a "fetching-mail"-job (imap) (deadlock...
Status: RESOLVED NOT A BUG
Alias: None
Product: kmail
Classification: Applications
Component: IMAP (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-15 19:51 UTC by Daniel Hahler
Modified: 2009-01-03 17:11 UTC (History)
1 user (show)

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 Daniel Hahler 2006-02-15 19:51:43 UTC
Version:            (using KDE KDE 3.5.1)
Installed from:    Ubuntu Packages

KMail's job status list had one entry "Fetching mail xxx.." for a long time (on an IMAP account).

I've clicked "cancel" to abort it and an "Error - KMail" disalog popped up, but has not been finished getting drawed. This is probably the "Connection to xxx is broken" message that I've seen before when canceling a job.

Now there seems to be a deadlock situation between some components, as KMail eats up all CPU and the whole application windows does not get redrawn.

When I move the half-painted error dialog, "ghost images" of it stay in the preview pane, but folder and messages list stay white all the time.

There's also the job status bar popup (which displays the currently active tasks) which stays plain grey without any text when moving the error popup dialog window over it.



dgb backtrace of "kmail" process:
#0  0x373c0df2 in QGList::findRef () from /usr/lib/libqt-mt.so.3
#1  0x373c2348 in QGList::removeRef () from /usr/lib/libqt-mt.so.3
#2  0x370c7030 in QPtrList<QObject>::removeRef () from /usr/lib/libqt-mt.so.3
#3  0x370c2b99 in QObject::removeChild () from /usr/lib/libqt-mt.so.3
#4  0x370c3ebd in QObject::~QObject () from /usr/lib/libqt-mt.so.3
#5  0x370888df in QGuardedPtrPrivate::~QGuardedPtrPrivate () from /usr/lib/libqt-mt.so.3
#6  0x35ba1605 in KIO::Job::~Job () from /usr/lib/libkio.so.4
#7  0x35bba4c2 in KIO::SimpleJob::~SimpleJob () from /usr/lib/libkio.so.4
#8  0x370c24d2 in QObject::event () from /usr/lib/libqt-mt.so.3
#9  0x3705b65a in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#10 0x3705b84c in QApplication::notify () from /usr/lib/libqt-mt.so.3
#11 0x37753c7d in KApplication::notify () from /usr/lib/libkdecore.so.4
#12 0x36fec967 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#13 0x3705cca1 in QApplication::sendPostedEvents () from /usr/lib/libqt-mt.so.3
#14 0x3705cda8 in QApplication::sendPostedEvents () from /usr/lib/libqt-mt.so.3
#15 0x36fffc17 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#16 0x37074153 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#17 0x3705a195 in QApplication::enter_loop () from /usr/lib/libqt-mt.so.3
#18 0x372771dc in QDialog::exec () from /usr/lib/libqt-mt.so.3
#19 0x35fd7660 in KMessageBox::createKMessageBox () from /usr/lib/libkdeui.so.4
#20 0x35fd7e0d in KMessageBox::createKMessageBox () from /usr/lib/libkdeui.so.4
#21 0x35fd8061 in KMessageBox::informationListWId () from /usr/lib/libkdeui.so.4
#22 0x35fd8169 in KMessageBox::informationList () from /usr/lib/libkdeui.so.4
#23 0x36005c26 in KMessageBox::information () from /usr/lib/libkdeui.so.4
#24 0x37cc9cce in KMail::ImapAccountBase::handleError () from /usr/lib/libkmailprivate.so
#25 0x37cd24eb in KMAcctImap::handleError () from /usr/lib/libkmailprivate.so
#26 0x37cc83de in KMail::ImapAccountBase::handleJobError () from /usr/lib/libkmailprivate.so
#27 0x37e15b68 in KMail::SearchJob::slotSearchResult () from /usr/lib/libkmailprivate.so
#28 0x37e164cb in KMail::SearchJob::qt_invoke () from /usr/lib/libkmailprivate.so
#29 0x370c526d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#30 0x35b8815c in KIO::Job::result () from /usr/lib/libkio.so.4
#31 0x35bd9532 in KIO::Job::emitResult () from /usr/lib/libkio.so.4
#32 0x35bd9676 in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.4
#33 0x35ba1be9 in KIO::SimpleJob::slotError () from /usr/lib/libkio.so.4
#34 0x35bdb17e in KIO::SimpleJob::qt_invoke () from /usr/lib/libkio.so.4
#35 0x370c539a in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#36 0x35b87313 in KIO::SlaveInterface::error () from /usr/lib/libkio.so.4
#37 0x35bf30f9 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4
#38 0x35b9a2e9 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4
#39 0x35b9eaf0 in KIO::Slave::gotInput () from /usr/lib/libkio.so.4
#40 0x35b9ec85 in KIO::Slave::qt_invoke () from /usr/lib/libkio.so.4
#41 0x370c526d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#42 0x370c5b7c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#43 0x374550f3 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#44 0x370e559a in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#45 0x3705b65a in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#46 0x3705b84c in QApplication::notify () from /usr/lib/libqt-mt.so.3
#47 0x37753c7d in KApplication::notify () from /usr/lib/libkdecore.so.4
#48 0x36fec967 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#49 0x3704d177 in QEventLoop::activateSocketNotifiers () from /usr/lib/libqt-mt.so.3
#50 0x3700072f in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#51 0x37074153 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#52 0x37074076 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#53 0x3705a169 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#54 0x0804a04b in ?? ()
#55 0x3fb2ff08 in ?? ()
#56 0x3fb300f4 in ?? ()
---Type <return> to continue, or q <return> to quit---
#57 0x00000000 in ?? ()
Comment 1 FiNeX 2008-12-26 19:15:52 UTC
Hi! Can you reproduce this bug using a more recent KDE version like 3.5.10 or KDE 4.2 beta 2?
Comment 2 Daniel Hahler 2009-01-03 17:11:31 UTC
No, I cannot reproduce it (and I could not reproduce it back then, too).

Since the backtrace is of no use with the recent development in KMail, I'm closing this bug as Invalid.

Thanks.