Bug 126894 - pop download hangs on "preparing transmission" with near 100% cpu usage
Summary: pop download hangs on "preparing transmission" with near 100% cpu usage
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Unmaintained
Component: pop3 (show other bugs)
Version: 1.9.1
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-07 11:40 UTC by Robert Persson
Modified: 2018-09-04 18:19 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 Robert Persson 2006-05-07 11:40:53 UTC 
Version:           1.9.1 (using KDE KDE 3.5.2)
Installed from:    Gentoo Packages
Compiler:          gcc-3.4.5 
OS:                Linux

Sometimes (but not always) kmail fails to fetch mail from one of my pop accounts. It pops up a "Preparing transmission from..." message and kontact's cpu usage hits near 100% until I manually cancel the fetch.

What should happen, of course, is that

(a) kmail should automatically abort a failed pop3 fetch (an old problem this -- see bug 104902).

(b) it shouldn't hog the cpu when it's doing nothing, particularly when it's doing some nothing that it shouldn't have been doing in the first place.

Normally kmail ends up being a cpu hog because I have it running a spamassassin check. Is it possible that spamassassin is the culprit here, going bananas trying to filter mail that hasn't arrived yet?
Comment 1 Thiago Macieira 2006-05-14 13:08:57 UTC 
Which process is taking lots of CPU time?
Comment 2 Robert Persson 2006-05-28 07:28:43 UTC 
kontact.
Comment 3 Martin Koller 2009-09-25 21:19:48 UTC 
Are you still seeing this problem with KDE 4.3.1 ?
Comment 4 Andrew Crouthamel 2018-09-04 18:19:43 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!