Bug 90811

Summary:	high cpu usage after running for some time
Product:	[Unmaintained] kmail	Reporter:	jalal <the_jalal>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description jalal 2004-10-05 17:09:23 UTC

Version:            (using KDE KDE 3.2.92)
Installed from:    SuSE RPMs
OS:                Linux

After running for some time ( < 1 hour) kmail cpu usage slowly rises, usually levelling out at 60-70%.

Running strace gives:

me@home $ strace -c -p 20890
% time     seconds  usecs/call     calls    errors syscall
------ ----------- ----------- --------- --------- ----------------
 89.43    1.087689          12     91261           gettimeofday
  7.35    0.089347        1015        88           write
  3.21    0.039091        1564        25           writev
  0.00    0.000040          20         2         2 unlink
  0.00    0.000012          12         1         1 rename
------ ----------- ----------- --------- --------- ----------------
100.00    1.216179                 91377         3 total

which seems to indicate some kind of loop.

Comment 1 Stephan Kulow 2004-10-06 11:45:10 UTC

Am Dienstag 05 Oktober 2004 17:09 schrieb jalal:

> which seems to indicate some kind of loop.
It doesn't indicate anything but that almost no time is spent
in syscalls

Greetings, Stephan

Comment 2 scragz 2004-10-10 05:25:55 UTC

Same thing happening to me with kmail 3.3 on Debian. This is particularly bad because I, and I assume many people do as well, leave my PIM open all of the time and it's very inconvenient to have to restart it at least once a day (I don't get as frequently as the bug reporter). I should add that I don't remember having this problem with 3.2.

Comment 3 jalal 2004-10-10 10:52:02 UTC

Wrote Stephan:
>> which seems to indicate some kind of loop. 
> It doesn't indicate anything but that almost no time is spent 
> in syscalls 

Nearly 100,000 function calls in a 5 second period sounds remarkably like a loop to me...
:)

Comment 4 Till Adam 2004-10-23 21:43:14 UTC

This sounds like the background expiry is kicking in and removing large amounts of messages. Can you guys confirm that?

Comment 5 Till Adam 2004-10-23 23:00:56 UTC


*** This bug has been marked as a duplicate of 89345 ***