On Tue, Apr 16, 2013 at 2:11 PM, Even Rouault <even.roua...@mines-paris.org> wrote: > I've investigated a bit and I've discovered that while computing overviews, > libtiff constantly switches from TIFF "directories" (main image, first > overview,second overview, etc...). While doing this, it calls each time client > code to install its own TIFF tags (libgeotiff for the geotiff tags, GDAL for > the > GDAL specific TIFF tags), but doesn't reset its array of existing tags. So > each > time the tags are added again and again, hence the huge memory allocation. > > Could you test the attached patch (assuming you build GDAL with internal > libtiff) ?
I can apply and test this on linux but don't know how to do it on windows. I usually use the nightly windows builds from Tamas. Should I test this on linux? > > It would be good if you could also open a ticket in Trac about that issue. I've opened a ticket, http://trac.osgeo.org/gdal/ticket/5054 Eli _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev