-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David W Smith wrote:
> So I reverted to SA 3.0.2 and the memory leak ceased rapidly plus > the load on the server normalized. > > The SA 3.0.3 install had both the URIDNSBL and the SPF module > enabled (the enabling of the latter was new (on my server) to the > 3.0.3 install and the memory leak continued with and without this > module enabled), as has the 3.0.2 install. These two comments seem to contradict, did reverting to 3.0.2 help or not? 3.0.3 removed a large memory issue with autowhitelist db files, but otherwise 3.0.3 contained VERY SMALL changes. Also, how are you calling SA? Are you sure it is a memory leak and not just a highwater mark? What sort of machine (memory wise) are you running SA on and how many children are you starting? Is the machine doing anything else? Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCndL4G4km+uS4gOIRAsjXAJsGyOJnwoyMTgt9SOZpDtDEbrylRACdF1LB 77mulc23GzAgHdsuhBhsrQM= =NiQ8 -----END PGP SIGNATURE-----
