I would like to know if the following behavior is expected:
- I instantiate an image reader (from disk)
- I configure and update() the reader to read a file
- I delete the file on disk used by the reader
- I call UpdateLargestPossibleRegion() on the reader.
The reader attempts to read the deleted file.
So my question is, why does the reader try to read the file if it has already read it ?
Are you explicitly providing an
ImageIO to the reader?
A minimal example and the explicit error or stack trace you are encountering could explain why you are getting the error.
Found it !
I had some code that was modifying the largest possible region of the reader output image as a side effect (because of a pointer/reference bug).
So the answer is no, UpdateLargestPossibleRegion() is not supposed to re-read the file if there is no reason to