Bug 138486 - kio_imap4 collapses when started under a high load
Summary: kio_imap4 collapses when started under a high load
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: kmail
Classification: Unmaintained
Component: IMAP (other bugs)
Version First Reported In: 1.9.5
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-07 07:54 UTC by Mathias Homann
Modified: 2010-01-01 22:43 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mathias Homann 2006-12-07 07:54:36 UTC 
Version:           1.9.5 (using KDE 3.5.5 "release 45.2" , openSUSE )
Compiler:          Target: x86_64-suse-linux
OS:                Linux (x86_64) release 2.6.16.21-0.25-default

whenever i start kontact in a situation where the machine is under a high load already (for example, on a suse 10.1 after the system has just booted up, all thanks to zmd), one or more of the started kio_imap4 processes hangs with 100% cpu usage, and kmail/kontact shows a message reading "connection to server XYZ has terminated or timed out".
There's no pattern to which of my ipap accounts show this behaviour in such a situation.
Killing the hanging kio_imap4 from within top leads to the point where  have to restart kmail/kontact, since it does not start a new one, as opposed to any other situation with crashing kio_imap processes.
System(s) here with that behaviour:
SuSE 10.1 with kde 3.5.5, one i686 box and one x86_64 box.
Comment 1 Björn Ruberg 2010-01-01 22:43:11 UTC 
Do you still have this issue in KDE 4.3?