[Bug 3981] New: spamd chews up all available swapspace after a time

[bu...@bugzilla.spamassassin.org]

http://bugzilla.spamassassin.org/show_bug.cgi?id=3981

           Summary: spamd chews up all available swapspace after a time
           Product: Spamassassin
           Version: 3.0.1
          Platform: PC
        OS/Version: FreeBSD
            Status: NEW
          Severity: critical
          Priority: P1
         Component: spamc/spamd
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: brian@backland.net


The Overview:
I was having a problem in 3.0.0 where eventually spamd would use up all 
available swapspace (1 GIG in this case).  I upgraded to 3.0.1 as the release 
notes mentioned a memory leak fix.  While it improved the problem slightly, 
the problem still exists.  This problem does not occur in V2.64, and for now I 
have down-graded to that version.

The Problem:
spamd uses up all swapspace after an indeterminent amount of time.  The time 
period it takes for this to happen is, I think, dependant upon the amount of 
mail being scanned.  I was using the default install for 3.0.0 and for 3.0.1, 
5 processes with 200 connections per child.  I tried lowering the number of 
connections per child as low as 2 and still eventually spamd used up all 
available swapspace.  I have run top and seen the spamd processes use up as 
much as 250MB of memory each, hence the reason they are chewing up all the 
swapspace.

System Info:
System-wide implementation of SpamAssassin V3.0.1 via /etc/procmailrc
FreeBSD 4.1-RELEASE #3: Tue Oct 12 00:38:16 EDT 2004
CPU: AMD Athlon(tm) Processor (857.65-MHz 686-class CPU)
  Origin = "AuthenticAMD"  Id = 0x642  Stepping = 2
Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT
,PSE36,MMX,FXSR>
  AMD Features=0xc0440000<<b18>,AMIE,DSP,3DNow!>
avail memory = 778989568 (760732K bytes)
Swap Device       1K-blocks  Used   Avail   Capacity  Type
/dev/da0s1b       1048448    22416  1026032     2%    Interleaved

I have seen answers to other memory bug reports suggesting adding more memory, 
but I don't believe a Window's solution will fix a UNIX problem.

Anything else you need, please let me know

Regards Brian



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.