Bug 151433

Summary: spamd generate child processes which occupies all memory
Product: [Fedora] Fedora Reporter: Marcin Draminski <mdramin>
Component: spamassassinAssignee: Warren Togami <wtogami>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3CC: felicity, jm, parkerm, reg+redhat, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: RHSA-2005-498 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-04-29 17:35:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 156390    

Description Marcin Draminski 2005-03-17 20:40:42 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2

Description of problem:
I'm trying to make evolution to use spamassassin, but when I download mails the spamd process generates several child processes which are eating all my memory.  To make it worse, after I have downloaded the mails those processes don't free any memory untill I kill them manually.

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

How reproducible:
Always

Steps to Reproduce:
1.start evolution
2.download mails from mail server
3.ram memory gets filled up completely
  

Actual Results:  memory filled up completely and I had to kill manually the spamd processes

Expected Results:  spamd processes should stop automatically and free all used memory

Additional info:

Comment 1 Warren Togami 2005-04-03 10:51:00 UTC
http://people.redhat.com/wtogami/temp/spamassassin/
Please test the fc3 RPM from here, which is 3.0.2 plus some patches that might
help with your memory consumption problem.

Comment 2 Warren Togami 2005-04-29 05:33:33 UTC
Please test the spamassassin-3.0.3 now in FC3 updates.

Comment 3 Marcin Draminski 2005-04-29 10:27:39 UTC
It works OK now, thanks.  Memory is occupied but then it is released.
Regs.
Marcin