Re: [gdal-dev] a possible memory leak in ogr\ogrsf_frmts\sqlite

2025-02-06 Thread Deyan Vasilev via gdal-dev
gt; explicitly freed before the end of the process, and the amount of it > doesn't grow over time. There are certainly many similar such patterns > in GDAL or other libraries it uses, and I don't see that as a bug or > something that requires code changes. > > Even >

[gdal-dev] a possible memory leak in ogr\ogrsf_frmts\sqlite

2025-02-06 Thread Deyan Vasilev via gdal-dev
Hello, I was chasing for a long time a small 8 byte memory leak and was able to identify it in the OGR sqlite extension binding, here's what I observed: A call to OGRSQLiteBaseDataSource::OpenOrCreateDB() would invoke OGR2SQLITE_Register() and then sqlite3_auto_extension(). The latter is a sqlite

Re: [gdal-dev] Thread-safe raster access

2024-06-05 Thread Deyan Vasilev via gdal-dev
Hi, I've written a piece of software that fetches tiles out of a single MBTiles raster done by multiple threads. Tiles go to a common cache which can be used by a "view" thread that assembles tiles on the screen in a seamless map. Each fetcher thread uses GDALOpenEx() and then RasterIO(GF_Read,,,)