[gdal-dev] Memory leaks?

[Simon Perkins]

On Mon, 2002-08-26 at 13:26, Simon Perkins wrote:
> Frank was offering to add some user code to free up this allocated
> memory in GDAL, if you know that you're going to be short of memory.
> This has to be a manual procedure though since only the user can know if
> GDAL will no longer be needed. But if you're on this hairy edge then
> you're almost certainly not going to have enough memory to actually load
> an image anyway, so I don't really see the point...

Just read Frank's e-mail. He sees the purpose of this function as an aid
to making hunting for real memory leaks less confusing. But I would have
thought that any decent memory leak checking software would only flag
leaks that occur in unreachable memory blocks, which does not include
those drivers. But it's been a while since I last used Insure for this
kind of thing.

Sy

-- 
Simon Perkins
Los Alamos National Laboratory, USA
http://nis-www.lanl.gov/~simes