I've had the problem happen starting Sunday morning with an automatic sa-update.
(I have until Sunday had it automatically sa-compile and restart after an 
update)

It affected various 64 bit machines; we only use 64 bit OSs on AMD64 quad and 
hex core machines. I use the Suse factory provided desktop kernels.

Opensuse 10.3, perl 5.8.8, SA 3.3.1, re2c 0.13.5
4x Opensuse 11.3, perl v5.12.1, SA 3.3.1, re2c-0.13.5-29.1.x86_64

My computers ran out of ram as a few of the spamd processes were using up 2GB of
ram each and not stopping, even with timeouts specified on the spamd startup. I
could watch the processes keep growing and not dying in top.

I turned off the automatic updating, restored from a recent backup 
/var/lib/spamassassin/, sa-compiled, and it's working great.

I'll wait for word that the stuff distributed via sa-update is fixed.

-Jason

On Mon, Mar 21, 2011 at 01:57:00AM +0100, Karsten Bräckelmann wrote:
> There are now reports, that this bug is not strictly related to 32 bit
> architecture (though always with compiled rules).
> 
> Since there have been offers for further testing: One data point is to
> collect details about systems, CPU architecture, instruction set used
> for compiling, versions (OS, kernel, compiler, re2c, Perl) and patch-
> level.
> 
> Another might be to reproduce the issue, and get a minimal test-case.
> 
> For that, can you reproduce the problem with trivial REs for the three
> __PILL_PRICE_x sub-rules?
> 
> Can you reproduce the problem by keeping (a renamed copy of) the
> original sub-rules and tflags, using a simple meta rule? Are two of them
> sufficient? Or even one?
> 
> 
> -- 
> char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
> main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
> (c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

-- 
/*
Jason Philbrook   |   Midcoast Internet Solutions - Wireless and DSL
    KB1IOJ        |   Broadband Internet Access, Dialup, and Hosting 
 http://f64.nu/   |   for Midcoast Maine    http://www.midcoast.com/
*/

Reply via email to