On Wed, Jun 22, 2005 at 01:35:39AM -0500, Damian Menscher wrote: > On Wed, 22 Jun 2005, Robert Stampfli wrote: > > >On Linux, with the new ClamAV 0.86, I'm seeing a significant > >jump in the size of clamav-milter (w/o --external) each time > >a new database is loaded. Is there per-chance a memory leak > >in the new code in this area? I did not observe this on > >earlier releases. > > How much memory usage are you seeing? A temporary increase (as much as > double) isn't unexpected, but it should go back down. > > For reference, here's what I see: > > At startup, it uses 9 meg of ram. > > Upon the first database update, ram usage increases to 15 meg. It > doesn't go back down, as I would have expected. > > Subsequent updates don't increase it further, however I did find that a > machine that had been running for a while was using 27 meg. I'm > guessing that increase was related more to the specific mails scanned > than to the database reloads, since, as I said, additional database > reloads didn't increase it past 15 meg. > > Tests were performed using clamav-0.86 running under RedHat 9 and RedHat > Enterprise 3.
After observing .86 (and .86.1) for several days, I must completely agree with Damian's assessment. clamav-milter seems to stablize, but at a memory size that is higher than previous releases, and the additional memory seems to be acquired during the first database update (something that did not happen before). Rob _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
