AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2010.03.02 20:38 "[Tiff] New Commiter", by Frank Warmerdam
2010.03.02 21:44 "Re: [Tiff] New Commiter", by
2010.04.01 21:12 "[Tiff] TIFFReadScanline and large compressed one-strip files", by Frank Warmerdam
2010.04.01 21:30 "Re: [Tiff] TIFFReadScanline and large compressed one-strip files", by Tom Lane
2010.04.01 21:52 "Re: [Tiff] TIFFReadScanline and large compressed one-strip files", by Chris Cox
2010.04.01 21:49 "Re: [Tiff] TIFFReadScanline and large compressed one-strip files", by Olivier Paquet
2010.04.02 07:29 "Re: [Tiff] TIFFReadScanline and large compressed one-strip files", by
2010.04.02 13:45 "Re: [Tiff] TIFFReadScanline and large compressed one-strip files", by Frank Warmerdam
2010.04.02 22:46 "Re: [Tiff] Tiff ReadScanline", by Richard Nolde
2010.04.05 13:02 "Re: [Tiff] TIFFReadScanline and large compressed one-strip files", by Edward Lam

2010.04.05 13:02 "Re: [Tiff] TIFFReadScanline and large compressed one-strip files", by Edward Lam

My client is finding that in some cases on 32bit systems there isn't 290MB of contiguous memory available and would like a way avoiding prereading the whole strip.

As a slight aside, are these Windows systems? I've run into situations before on Windows where I needed to "rebase" on all my .dll's to reduce virtual address space fragmentation. I just noticed that there's a new handy utility for determining such situations here: http://virtualmemorymapview.codeplex.com/ I haven't tried it yet though. In the past, I've hand rolled my own.

Of course, this is only at best a workaround but I relatively low effort one if it works for you. :)

Regards,

-Edward