Le jeudi 26 juin 2014 16:14:03, Simon Richard Proud a écrit : > Hi, > Have you noticed any other memory leaks in the MSG driver? We have seen > some huge memory uses when working with the visible MSG channels > (converting from DN to Reflectance) but have not been able to track down > where the memory is being used. Would be good to have a second opinion!
Simon, I just wanted to mention I can be available for contractual support on GDAL if you need. It might not be to be excluded that the leak might be in the Eumetsat library itself. Best regards, Even > > All the best, > Simon > > ________________________________________ > Fra: gdal-dev-boun...@lists.osgeo.org [gdal-dev-boun...@lists.osgeo.org] > på vegne af Christian Authmann [authm...@mathematik.uni-marburg.de] > Sendt: 26. juni 2014 05:23 > Til: gdal-dev@lists.osgeo.org > Emne: [gdal-dev] MSG Driver: two memory leaks > > Hello, > > valgrind'ing my application revealed two memory leaks in msgdataset.cpp. > > a) MSGDataset::pszProjection shall always point to a valid string during > the lifetime of the object; the old string needs to be released before > getting a new one from exportToWkt(). > > b) A spatial reference is exported to a temporary string as WKT, but the > string is never released. > > > Attached you'll find a patch fixing both; valgrind confirms that both > memory leaks are gone. > > > -- > Christian Authmann > Philipps-Universität Marburg > Fachbereich Mathematik und Informatik > AG Datenbanksysteme > Hans-Meerwein-Straße > D-35032 Marburg > _______________________________________________ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/gdal-dev -- Geospatial professional services http://even.rouault.free.fr/services.html _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
