Rather severe issue with an unmidified installation of spamassassin. Over time the spamd child processes don't terminate and just continue to grow and grow over time until the kernel starts terminating processes on the machine. SpamD uses 50MB by default and then just grows slowly over time as if there is a memory leak. Uses 50MB just after being run, an hour or so later is was using 100MB, then 175, etc etc. Also, there are 45 rulesets installed by default which the spamassassin people don't seem too happy about as they aren't actually part of the base spamassassin package, it also bloats the execution so the process uses 50MB when it is first run rather than 16MB so it may be worth having a use flag which needs to be added if you want these compiled in with SA rather than having to specify "+minimal" to not install them (although I'm not sure if +minimal does actually stop them from being installed).
What version of perl and when did you first notice this? I ask because there is a known issue with perl 5.8.8 and UTF8.
Wow. I'm seeing spamd use lots of memory too here (up to 2 threads of 10% of my 512MB of ram)... this is not a "good thing" for my laptop using Suspend2 to hibernate. I am using the -m 1 flag option too. (Two threads using 10% of my ram upon startup without even starting to filter mail yet.)
(In reply to comment #0) > Also, there are 45 rulesets installed by default which the spamassassin people > don't seem too happy about as they aren't actually part of the base > spamassassin package They are shipped with SA. ergo, we install them. I don't doubt the memory problems - I just can't dup them and have no errors to work with here that would indicate it is a problem with the ebuild....
What Mike said.
