Sorry to say, but 4.0a4 still leaks memory with our configuration. My question to other users: Do they observe this, too? If so, this would be worth to track down. Tools like valgrind impose load and risk for a production system. Another idea are wrapper functions (e.g. safe_malloc for malloc ...) and have some statistics with these, but this would imply global code changes, and thread locking would be an issue. Michael
Message
Re: [milter-greylist] memory leak or normal behaviour?
2007-05-11 by Michael Fromme