manu@... wrote: > Matt Kettler <mkettler@...> wrote: > >> I gave dnsrbl.c a casual eyeball-check yesterday, and I didn't see any code >> paths that would cause leaks, but your right, they might be there. >> >> I also ran it through splint, which was perfectly happy with it. >> >> Maybe tonight I'll give it a deep eyeball-check after I get home.. > > Maybe a problem in a library? > Maybe.. libbind has been known to have leaks before. That might be why my release of RH doesn't include libbind by default. FWIW, I ran overnight last night with only one DNSBL enabled. Overnight MG did grow, but very little.
Message
Re: [milter-greylist] memory leaks in 3.0 (release)
2006-12-13 by Matt Kettler