Dennis Davis wrote: [...]
Some on this list recommended reducing --max-conn-per-child from the default of 200 to reduce possible memory leakage in earlier versions of SpamAssassin. I doubt that this is a problem now, but it might be worth trying as a precautionary measure.
I am absulotely CERTAIN that memory leakage is a huge problem at the moment. Using SpamAssassin 3.0.2 for threee month I witnessed no problems at all, but on two consecutive days memory-usage went through the roof and killed my server. There is no AWL and even with Bayes disabled some spamd-processses reached up to 400MB of memory usage. After setting "--max-conn-per-child=20" I haven't seen more than 200MB for a single spamd, which is five or even six times as much as usual (littel bit more than 30MB).
Stephen M. Przepiora, David Stern and Johann Spies confirmed that they have seen "memory-usage going BOOM" recently, being forced to add more memory, to tune --max-conn-per-child" or just killing every child growing over a certain threshold. That's what I'd consider to be "4 reports of suspected memory leakage in a single day".
Personally I still consider 3.0.2 a recent version of SpamAssassin and scanning through the Canges of 3.0.3 I didn't find "fixed huge-memory-leak, upgrade ASAP!"....
I suppose there are spams sent to my server that trigger a SpamAssassin-bug. I don't know wheter the spammers really know that they trigger a memory-leak, but if they do, I expect that all of us will have to face a huge problem quite soon.
-- CU, Patrick.
