2021.04.23 13:46 "[Tiff] "TIFFAdvanceDirectory": Error fetching directory count .....getting fewer "frames" but still working..", by Pablo Conesa

2021.04.23 13:46 "[Tiff] "TIFFAdvanceDirectory": Error fetching directory count .....getting fewer "frames" but still working..", by Pablo Conesa

Hi! Not sure if this is the right place to report this. If not I'd appreciate advice

We are using a binary file that I believe is using libtiff lib (probably bigtiff).

While using it, we are getting lots of: TIFFAdvanceDirectory": Error fetching directory count

The thing is the tiff files we are reading are meant to have 50 "frames/pages" inside. (11k x 5K size)

The software, somehow does not detect the 50 frames, but still is able to process the tiff file with less frames, 35, 14....(seems random)

This software is used under a stressed system where huge tiff files are written in a network share and processed as soon as they are ready from another machine.

I've checked now (system is relaxed), and all the files have 50 frames (reported by python tifffile package) but my wild guess is that during the processing (stressed status) frames detected are less but still software "Works"?

Does this make any sense?

Is the tif file format valid when is partially written? Let's say file it's not being "finished" but processing has started?

or, under an stressed I/O (network environment), even if the tiff file is finalized, reading it could render "partial" reads like behaving as a 14 pages tiff when if is actually a 50 pages file?

All the best, Pablo.