On Tue, 2004-09-14 at 09:42, Jason Haar wrote: > On Tue, Sep 14, 2004 at 08:38:57AM +0100, Trog wrote: > > A few people (out of the thousands who run ClamAV) have reported "memory > > leaks" in stable versions of clamd. > > > > However, none of those people have submitted a report from a memory > > debugging tool to show where the leak occurs on their systems, despite > > being asked to by the development team. None of the development team > > have seen such a leak. > > > > I tried to help out with valgrind as you suggested - but within 10 mins it > took 1.5Gb of RAM on my workstation (I wasn't going to put it up on > production now was I? :-) and - well - I turned it off. I really don't have > the equipment to handle running 1.5Gb debugging processes...
On my 512MB FC-1 system: %MEM VSZ RSS COMMAND 12.8 1566524 66012 valgrind --leak-check=yes --tool=memcheck clamd The virtual size may get up to 1.5GB, but the resident size (which is the actual amount of memory it is using) shouldn't. So, unless you are running with No-Overcommit Memory settings, which certainly isn't required on a workstation (and is of arguable use at all) it shouldn't be an issue. Apart from that, even running it for 10 mins may be enough to show a problem. Did you generate a result, or just kill it? -trog
signature.asc
Description: This is a digitally signed message part
