You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When iv opens an image file that was only partially written -- for
example, an EXR that a renderer crashed on or was killed before it
finished writing the pixel data -- the read fails and iv refuses to
display anything at all.
Now, if the straightforward read fails, iv reopens the file with the
existing "oiio:missingcolor" config attribute set to black, which asks
the OpenEXR reader to fill unreadable scanlines or tiles with that color
instead of failing the read. Readers without that support ignore the
config, so the re-read simply fails the same way for them. In the
partial case, the status bar displays a note explaining that the file is
only partially readable.
For images that were read through the ImageCache (where pixel data
isn't touched until display time), a cheap probe of the last scanline
or tile checks that the pixel data is intact, and falls back to the
re-read if it isn't.
One prerequisite fix along the way: a failed multi-scanline chunk decode
with oiio:missingcolor set re-entered the per-scanline retry, which
re-entered the chunk cache until the stack blew up -- the per-scanline
retry now bypasses the chunk cache, fixing that for missingcolor users
too and making the iv fallback actually work on compressed multi-
scanline files.
Fixes#4713
Assisted-by: Claude Code / glm-5.3-flash
Signed-off-by: linsen <251731047+linsen458-spec@users.noreply.github.com>
0 commit comments