Red Hat Bugzilla – Bug 158807
forkbomb-like behaviour observed with Evolution spam checking
Last modified: 2007-11-30 17:11:06 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050504 Fedora/1.0.3-4 Firefox/1.0.3
Description of problem:
From this report on fedora-test-list:
"The other problem I was seeing on a regular basis was all the resources
of the machine being consumed such that I could not get to an alternate
console, run ps or top, the machine was dragged to its knees. I'm pretty
sure evolution in concert with spamd (filter incoming mail checkbox) was
the culprit, but given how hard it was to do anything when the problem
occurred I only have anecdotal evidence. I was often forced to resort to
using the reset button. I suspect it was some type of fork bombing with
spamd where it got caught in tight loop launching processes that would
immediately die, but that's only speculation. I have not seen this
problem since turning off the filter option on incoming mail.
I've talked to David Malcom about this and he encouraged me to file a
bugzilla, but it so hard to collect any information or see a pattern
that I wasn't sure I saw the value in a bug report that simply asserted
"evolution is doing something bad" ;-) "
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run Evolution
2. In Edit->Settings->Mail Preferences->Junk, enable the "Check incoming mail for junk" checkbox
John: please can you confirm I got the details correct, and confirm the version
of evolution and spamassassin that you're seeing this with. Thanks.
Is this problem still present in Fedora Core 6?
I have not seen this behavior in a while
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
Fedora Core 3 and Fedora Core 4 are no longer supported. If you could retest
this issue on a current release or on the latest development / test version, we
would appreciate that. Otherwise, this bug will be marked as CANTFIX one month
from now. Thanks for your help and for your patience.
I have not seen this behavior in a long time, it's safe to close this.