[Bug 275420] Sometimes Kontact and dbus-daemon hog two of my 6 cores with 100% each - killing Kontact solves this

[michael at linuxmagic.com]

https://bugs.kde.org/show_bug.cgi?id=275420


michael at linuxmagic.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |michael at linuxmagic.com




--- Comment #3 from  <michael linuxmagic com>  2011-08-24 18:42:19 ---
Application: kontact (4.4.7)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.3
Operating System: Linux 2.6.32-trunk-686 i686
Distribution: Debian GNU/Linux 6.0.2 (squeeze)

-- Information about the crash:
<In detail, tell us what you were doing  when the application crashed.>

The crash can be reproduced every time.

 -- Backtrace:
A useful backtrace could not be generated

Report to https://bugs.kde.org

Just to note, this may not be related to this bug, but I use Kontact with about
10 IMAP accounts, and some of those are shared IMAP accounts, and every 2 days
I  have to close kmail/kontact and then manually kill all the processes.. about
6-20 processes hand around, and kontact also hangs around.  From the GUI, if
you make the mistake of trying to start kontact, it appears to try to start,
then dies silently, no warning that another kontact instance is still running. 
The IMAP processes seem to be stuck on: select(4, [3], [], NULL, NULL, while
the kontact process is hung with:

read(8, 0x8268d68, 4096)                = -1 EAGAIN (Resource temporarily
unavailable)

and it loops.. It also seems that the reason we get the system CPU runaway, is
that the kontact process keeps spawning new IMAP connections, but doesn't close
the legacy ones that it lost contact with or is waiting on..

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.