Opened 20 years ago

Last modified 18 years ago

#193 closed defect (fixed)

Memory leaks in the GDAL Drivers and the Manager

Reported by: paul@… Owned by: warmerdam
Priority: highest Milestone:
Component: default Version: unspecified
Severity: critical Keywords:
Cc:

Description

There is no user controlled clean up implementation in the current GDAL library 
to clean up the registered drivers and the driver manager. This results in a 
memory leaks that needs to be addressed.

Attachments (1)

modis_snow_vmap0_wgs84_gdal.png (92.5 KB ) - added by neteler@… 18 years ago.
MODIS gdalwarp result vs VMAP0 (both WGS84)

Download all attachments as: .zip

Change History (3)

comment:1 by warmerdam, 20 years ago

Added GDALDestroyDriverManager() method to destroy the driver manager, 
and all registered drivers.  This should almost cleanup all memory, the only
exception seeming to be the "finder" location stack.

For testing purposes gdalinfo.c now uses this function. 


by neteler@…, 18 years ago

MODIS gdalwarp result vs VMAP0 (both WGS84)

comment:2 by neteler@…, 18 years ago

(From update of attachment 226)
sorry, wrong bug number.

Note: See TracTickets for help on using tickets.