LibTiff Mailing List
TIFF and LibTiff Mailing List Archive
October 2009
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
2009.10.20 14:06 "Re: Limit to the number of files loadable in LibTiff", by Simon R Proud
>> >> Looking at the source, the message is generated if >> TIFFSetupStrips(tif) fails. This in turn fails if _TIFFmalloc() fails. >> So it sounds like you are running out of memory. I would try watching >> your program with "top" as it runs and see how large the RSIZE column >> gets. > >It is certainly a resource issue. Either due to a leak or using too >much of something. Since you are using Linux you mean be able to use >the 'memusage' facility to help understand memory usage: Yep, it definitely isn't a libtiff issue! I have discovered that as I was running 32bit linux I can't access the whole 8Gb of memory, but now that I have switched to 64bit the problem appears to be gone. I'm no longer getting the buffer message. >And for detailed analysis, use > > valgrind --tool=memcheck --leak-check=full yourprog > >to check for leaks, and use > > valgrind --tool=massif yourprog > >to find areas of excess consumption. Thanks. They show no leaks in the code, I think the problem is simply that I'm crunching a LOT of data concurrently and I simply exceeded the memory limitations. Anyway, as I say it works now. Thanks for the help, guys! Much appreciated. PhD Student Department of Geography ุster Voldgade 10 University of Copenhagen DK-1350, Copenhagen Denmark Email: srp@geo.ku.dk