Le mercredi 06 avril 2016 15:21:24, Julian Zeidler a écrit :
> Hi Even,
>
> Thank you for the the very quick and very helpful reply. I spent the
> whole day yesterday trying to find the memory leak in my code that
> caused 11GB Ram usage. ;-)
> One quick follow-up would setting GDAL_DISABLE_READDI
Hi Even,
Thank you for the the very quick and very helpful reply. I spent the
whole day yesterday trying to find the memory leak in my code that
caused 11GB Ram usage. ;-)
One quick follow-up would setting GDAL_DISABLE_READDIR_ON_OPEN =
EMPTY_DIR break reading from vrt or envi files with a hea
Julian,
I addressed a similar use case some time ago in GDAL 2.1 with
https://trac.osgeo.org/gdal/changeset/32242
For previous versions, you can set GDAL_DISABLE_READDIR_ON_OPEN = YES as
environment variable / configuration option.
And if you don't need checking for any side-car file at all, you
Hey all,
I have the Problem that my cpp-Code which exclusively uses gdal for IO
suddenly uses vast Amounts of memory in a production environment.
When i analyzed the memory foot-print (via valgrind massif) it turns
out that 95% (in the test case ==7.8GB! RAM) is allocated by gdal in
GDALDefau
