2006.02.13 18:50 "Re: [Tiff] Memory leak in TIFFOpen on Win32 ?", by Thierry Pierron
On Feb 13, 2006, at 11:05, Bob Friesenhahn wrote:
There are two different I/O subsystems which work in the Windows build. Besides the tif_win32 module, the tif_unix module may be used under Windows. The leak may be I/O subsystem related so it is particular to the Windows platform. Which one of these does the GnuWin32 libtiff use?
Well, strange. I recompiled libtiff using source file that comes aside binary installer. I try the two versions (one with unix IO calls and the other with Win32 api) and it worked fine, no more memory leak (with prebuilt binary, the test I do eats up to 20 Mb after 10000 iterations). I only tried a static link, not yet a dll.
Is there a way to know which options were used for compilation of binary package (tif_config.h)? I would be insterrested in what is causing so much memory leak.