Re: [gdal-dev] Call to GDALDestroy results in occasional core dump, GDAL 3.4.2

Just for fun, I changed by code back to cause the crash again. Now it’s difficult to reproduce but here is the part of the callstack showing where the issue occurs. The CPLCleanupTLSList function is the function of interest as it loops over some type of list. Within a conditional it is adding

Re: [gdal-dev] Call to GDALDestroy results in occasional core dump, GDAL 3.4.2

On Wed, Sep 18, 2024 at 8:32 PM Fox, Shawn D (US) via gdal-dev < gdal-dev@lists.osgeo.org> wrote: > In our case we have a singleton class that acts as a façade and all of our > calls to GDAL Apis are done by the methods of this class. The rest of our > code base only interacts with the singleton

Re: [gdal-dev] Call to GDALDestroy results in occasional core dump, GDAL 3.4.2

In our case we have a singleton class that acts as a façade and all of our calls to GDAL Apis are done by the methods of this class. The rest of our code base only interacts with the singleton so that we only have one project that actually depends directly on the GDAL library. Since the _insta

Re: [gdal-dev] Call to GDALDestroy results in occasional core dump, GDAL 3.4.2

There are many potential causes. Providing code and a backtrace would allow someone else to look. On Wed, Sep 18, 2024, 7:28 PM Fox, Shawn D (US) via gdal-dev < gdal-dev@lists.osgeo.org> wrote: > Could someone help me understand this sentence from the documentation at > gdal.h: > Raster C API —

Re: [gdal-dev] Call to GDALDestroy results in occasional core dump, GDAL 3.4.2

Le 18/09/2024 à 18:27, Fox, Shawn D (US) via gdal-dev a écrit : Could someone help me understand this sentence from the documentation at gdal.h: Raster C API — GDAL documentation for the GDALDestroy function? “Since GDAL 2.4.0, this functi

[gdal-dev] Call to GDALDestroy results in occasional core dump, GDAL 3.4.2

Could someone help me understand this sentence from the documentation at gdal.h: Raster C API - GDAL documentation for the GDALDestroy function? "Since GDAL 2.4.0, this function may be called by application code, since it is no longer called au