[gdal-dev] memory leak in GRIB reader (with Python bindings)

[Even Rouault]

Le jeudi 24 mai 2012 23:47:14, Chris Barker a écrit :
> On Thu, May 24, 2012 at 2:40 PM, Even Rouault
> 
> <even.rouault at mines-paris.org> wrote:
> > Ok, see http://trac.osgeo.org/gdal/ticket/4682 for a fix. Basically, the
> > current caching strategy is maintained (cache all bands that have been
> > accessed), until a threshold is reached (arbitrarly set to 100 MB by
> > default).
> 
> seems reasonable -- is there an API to change that threshold at run
> time? Not I think it's needed...

Yes, there's a config option, GRIB_CACHEMAX, that you can set if necessary 
(value in megabytes, and applies for each dataset). I didn't advertize it in 
the doc for now, as I think there are virtually no use case where you would 
need to alter it. (unless you open at a dozains of huge grib files...)