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. So thus far I don't have any leads as to why it's happening. Any C coders on the list are invited to take a look; perhaps a new set of eyes is what's needed. -MSK ------------------------------------------------------------------------------ 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
