On Thu, 2004-03-25 at 02:52, Kelsey Cummings wrote: > On Tue, Mar 23, 2004 at 03:17:11PM -0500, Jesse Guardiani wrote: > > Lucas Albers wrote: > > > > > I'm a bit hesitant of upgrading to .68 or .70-rc if it appears to have a > > > memory leak. At what point can the developers say: > > > "this x release does not have a memory leak." > > > > :) Never, or about 2 years after the software is released and has run on > > virtually every machine known to man. That's my experience with C anyway. > > Well, there are little leaks and BIG leaks. This is a severe leak > resulting in over 1GB used in 10 hours or so. > > Any comments from our truly wonderful devs?
Well, you appear to be the only one seeing a leak. We (the devs) do check for memory leaks quite frequently, and so are pretty sure there are no big leaks. It could be a leak in your libc, or some other library. I would suggest you use valgrind to check for were the leak is. -trog
signature.asc
Description: This is a digitally signed message part
