Trog wrote:
On Wed, 2005-05-11 at 14:03 +0200, Martin Blapp wrote:
Seems not to be the case. Valgrind doesn't do anything after that, maybe waiting in a deadlock condition. I've now waited 10 minutes, truss -p PID doesn't show any activity.
If I wait 10 minutes for clamd finishing its activity and then connect with telnet sending QUIT it works ... but then valgrind doesn report any problems anymore.
So it's not leaking memory then.
Hi,
Just as an FYI, I had upgraded to the CVS version (Changelog shows Wed May 4 20:15:33 BST 2005 (njh)) to work around the password protected zip file problem.
The next morning, clamd was using 638 megs of memory on the system. I killed it and restarted and 2 hours later it was using 350 megs.
I patched 0.84 to allow for the !encrypted flag instead and clamd is sitting here happily using 13 meg as usual after 4 days.
Just FYI, while it may not be *leaking* memory, it doesn't seem to be freeing it as well.
Regards,
Rick _______________________________________________ http://lurker.clamav.net/list/clamav-devel.html
