Bug 138486

Summary:	kio_imap4 collapses when started under a high load
Product:	[Unmaintained] kmail	Reporter:	Mathias Homann <Mathias.Homann>
Component:	IMAP	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED WAITINGFORINFO
Severity:	normal	CC:	bjoern
Priority:	NOR
Version First Reported In:	1.9.5
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

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?