Bug 81156

Summary: 100% CPU, slow mailfetching, huge memoryusage and loss of mails
Product: [Unmaintained] kmail Reporter: Bjarne Wichmann Petersen <kde.nospam>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: FreeBSD Ports   
OS: FreeBSD   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Bjarne Wichmann Petersen 2004-05-08 19:09:35 UTC
Version:            (using KDE KDE 3.2.2)
Installed from:    FreeBSD Ports
OS:          FreeBSD

This may be a dupe of bug #75045, #75386, #78794, #80410 and/or #81104

This may also be several bugs or just one.

This is what is happening:

I open kmail and start fetching my mails. Since 3.2 that means fetching mails from 6-7 pop3-boxes simultaniously from 3 different servers and 200+ messages. Kmail becomes unresponsive and each message takes 1-5 sec. to download(1). Top shows that kmail is consuming all available CPU-time and between 150-200 MB of RAM. In idle-state it consumes 100+ MB (is that normal?).

I've also noticed that I'm not receiving all the mails I ought to; seamingly in a random unreproducable fashion. I've tried sending myself loads of mails and receiving them all, while mailinglist I'm subscribing to show several "blanks" in the threads. I estimate I'm not receiving 1-5% of the mail.(2)

I'll try to attach a gdb-output when/if I figure out how to do that.

(1) This mostly happens when there are many mails to be fetched. When I only check out one mailbox or there isn't that many messages kmail can be quick about it, but it may also show the above behaviour.

(2) Until now, I've only seen this behavior from one mailbox, but it's also receiving 99% of my mails. But it's hard to tell from the other mailboxes since I don't know what I'm not receiving.
Comment 1 Tom Albers 2004-09-12 12:24:28 UTC
Could you upgrade to kde 3.3 and see if this still happens?
Comment 2 Philip Rodrigues 2006-10-29 19:41:41 UTC
Feedback timeout. If the problem still occurs with the latest KMail, please reopen, thanks!