Kevin F Webb wrote:
Good day!
I am experiencing a memory leak from looped calls to GDALRasterIO(). It
may be something I am doing improperly
because I use/call RasterIO() in a C++ program that runs leak free.
I "migrated" the C++ code to the GDAL C API so that I can integrate some
really old C code downstream from the GDALRasterIO() call.
The leak was observed on v1.5.2, so I upgraded to 1.7.2 and am
experiencing the same effect.
Are there special options or considerations when compiling C code
against the GDAL library?
Kevin,
You haven't shown your code, but I suspect you aren't closing the
datasource and so the block cache isn't getting cleaned up.
Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmer...@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | Geospatial Programmer for Rent
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
