Bug 158949

Summary:	IMAP checking uses too much CPU
Product:	[Applications] kmail	Reporter:	Daniel O'Connor <darius>
Component:	IMAP	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	bjoern, finex, lemma
Priority:	NOR	Keywords:	triaged
Version:	1.9.8
Target Milestone:	---
Platform:	FreeBSD Ports
OS:	FreeBSD
Latest Commit:		Version Fixed In:

Description Daniel O'Connor 2008-03-08 06:07:07 UTC

Version:            (using KDE 3.5.8)
Installed from:    FreeBSD Ports
Compiler:          gcc version 4.2.1 20070719  [FreeBSD]
 
OS:                FreeBSD

kmail (standalone and in kontact) uses a lot of CPU (eg 40% of my Pentium-M 1.4GHz) when checking email. I find this pretty surprising because I would have thought it would be a bandwidth limited task.

I don't really know what I can try to work out what it's spending it's time doing though :(

Comment 1 FiNeX 2008-03-08 11:29:55 UTC

Are you using some antispam software such spamassassin?

Comment 2 Daniel O'Connor 2008-03-08 12:31:38 UTC

Nope, just checking an IMAP account (disconnected mode).

I do have a reasonable amount of mail - 5000 messages max in a given folder, 160k messages total, 180 mailboxes, but it doesn't appear to be related to mailbox size.

Comment 3 Thomas McGuire 2008-03-13 19:04:54 UTC

Could be the same as in bug 115331. Try the workaround in comment 8 there.

Comment 4 Daniel O'Connor 2008-03-17 04:13:12 UTC

Makes no difference unfortunately :(

Comment 5 Michael Leupold 2009-04-04 10:12:00 UTC

I can't reproduce this bug using trunk r948809. However if this is related to mailbox size I can't check it because I currently don't have any imap folder that big.

Can you still see the CPU usage going up on a recent release (eg. KDE 4.2.x)?

Comment 6 Björn Ruberg 2010-01-15 01:28:14 UTC

Waiting for an answer

Comment 7 Andrew Crouthamel 2018-09-04 18:23:55 UTC

Hello! Sorry to be the bearer of bad news, but this version of Kmail has been unmaintained for many years so I am closing this bug. Please try using the latest version of Kmail to see if your issue persists. If it does, please submit a new bug in "kmail2". Thank you!