LibTiff Mailing List
TIFF and LibTiff Mailing List Archive
November 2008
Previous Thread
Next Thread
Previous by Thread
Next by Thread
Previous by Date
Next by Date
Contact
The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems
Thread
2008.11.14 19:11 "Re: Memory leak (TIFFOpen, TIFFReadTile)?", by Frank Warmerdam
Ilkka Korpela wrote: > Quoting "Bob Friesenhahn" <bfriesen@simple.dallas.tx.us>: > > Bob > > Thanks. I found a way out of the memory consumption > by calling TIFFClose() and TIFFOpen in between rows of > TILES (inside the double loop). This way the consumption > (leak) stays < 25 MB with these huge images, which is > tolerable. Memory is freed when TIFFClose() is called. > > ilkka Salo Finland ilkka, It really sounds like you are mixup up process size with heap memory use. Many tools that report a processes size will also report all the memory currently used by pages of a disk file that are paged into memory as part of the io subsystem. This is not real heap use, and the memory will be released by the operating system as soon as it is needed for something else. Till then the disk pages are left in memory in case they are needed again. This is consistent with the memory use dropping on close. In my opinion, some care should be taken before reporting "memory leaks" based on summary process memory use tools. I generally disregard these sorts of reports under the assumption the reporter just doesn't know what they are doing. Best regards, -- ---------------------------------------+-------------------------------------- I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com light and sound - activate the windows | http://pobox.com/~warmerdam and watch the world go round - Rush | Geospatial Programmer for Rent