Bug 248322 - mail-notification took 98% CPU during mail check when network connection down
Summary: mail-notification took 98% CPU during mail check when network connection down
Alias: None
Product: Fedora
Classification: Fedora
Component: mail-notification   
(Show other bugs)
Version: 7
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Thorsten Leemhuis
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-07-16 03:23 UTC by Edmond Hui
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-07-16 04:41:06 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Edmond Hui 2007-07-16 03:23:33 UTC
Description of problem:

When network is down, mail-notification seem struck checking email and took 98%
of CPU.

Version-Release number of selected component (if applicable):

How reproducible:


Steps to Reproduce:
1. setup mail-notification to check email every 15 min (I have gmail and POP3)
2. disconnect network
3. wait for the next mail check, run top to see mail-notification used up all CPU %
Actual results:

98% of CPU is used by mail-notification as reported by top

Expected results:

it should continue to check email, but CPU usage should be much lower.

Additional info:

Comment 1 Thorsten Leemhuis 2007-07-16 04:41:06 UTC
This is likely not a Fedora-specific problem. Thus I'd like to ask you to
participate upstream to help getting this fixed for all distributions.

There is a bug already; see

The upstream maintainer is looking for somebody who find a good way to reproduce
it (I've seen the problem myself in the past, but only very sporadically)

Note that there is mail-notification 4.1 in updates-testing; it should land in
update-proper with the next push. Try that one please as well.

Comment 2 Edmond Hui 2007-07-16 22:08:29 UTC
I will test the latest (just received it over yum) and report back.

Thanks for the help

Note You need to log in before you can comment on or make changes to this bug.