On Wed, 27 May 2009, Murray S. Kucherawy wrote:
; I've observed a similar thing on all platforms. ; ; To try to come up with an explanation, I ran the filter after compiling it ; with valgrind on Linux and it reported no memory leaks; everything it ; reported was easily explained. Nevertheless, there's no obvious ; justification for the size to which the process gets after running for a ; while. ; ; I've done some code review work on it as well and haven't managed to ; discover any leaks in dkim-filter, libdkim or libar. I tried compiling it ; with the stock resolver instead of libar as well and that didn't improve ; anything. I use libdkim with libar in my own application and don't see this behaviour at all. The milter signs around 700 messages an hour and verifies up to 18,000 an hour. Running since May 20th, PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP 506 reci 14M 6536K sleep 59 0 0:35:49 0.0% ci-milter/15 This would seem to point to the filter component as being the leaky part.. A. ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
