On Thu, 25 Apr 2002, Matt Sergeant wrote: > On Wednesday 24 Apr 2002 8:02 pm, Viraj Alankar wrote: > > Thanks, I've made these changes and the memory usage does not seem bad. It > > still grows a little, reporting about 26M via top, but definitely not as > > bad as before. I will do some tests with creating new Mail::SpamAssassin > > objects instead of re-using one to see if there is any difference in memory > > usage. > > > > I did come across a small message (about 80k), that just causes > > spamassassin to hang. This message seems to have ALOT of blank lines in it. > > I've put it up here: > > > > http://www.cse.fau.edu/~valankar/blah.gz > > > > Didn't debug this much, but I did disable network checks and still the same > > hang result with this message. > > Now that's interesting. I wonder if it's constructed specifically to make SA > hang... I guess we need to redo the body test parser to grep out blank lines. > *sigh*
Is there anything that can be done to -avoid- this? Perhaps wrapping the regex portion of SA in an alarm() timer so that long-running regexes just get exited from? -- Charlie Watts [EMAIL PROTECTED] Frontier Internet, Inc. http://www.frontier.net/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
