2017.06.27 20:51 "[Tiff] Excessive memory allocation while chopping strips", by Nicolas RUFF

2017.06.28 18:08 "Re: [Tiff] Excessive memory allocation while chopping strips", by Paavo Helde

On 28.06.2017 18:22, Olivier Paquet wrote:

I think you misunderstood me. I meant the problem that uncompressed strip size can be quite large and, as far as I know, can't be validated without decompressing the data. A hard limit on strip size would cover that neatly and sane applications will keep it reasonable anyway.

If I had a vote a would vote against imposing arbitrary size limits. For example, our company is making software for customers which includes libtiff and the customers expect it to read *any* TIFF file which they happen to throw on it, both now and 10 years in the future. If the software does not cope with it, they blame us and don't care this is because we have forgotten to switch on some obscure flag first appearing in libtiff version x.y.z and which would have restored the libtiff capability to read any files it is capable to.

And yes, these are the customers having 20 GB TIFF files (has happened) and 10 GB strips (will happen soon). There is no "sane" limit.

Best regards