if mpv encounters one of these busted gifs, a selection of quiet-but-spammy 'I don't know what happened, but MPV just reported a weird error, here it is' logging no longer happens.if you see a file like that, try right-clicking and hitting manage->maintenance->regenerate file metadata. you may have seen this sort of error before where an mpv window seems to keep rendering the gif despite the scanbar hitting its right end.

as well as rendering, the duration and frame-counter code also handles these borked frames better, so animated gifs that have a single borked frame should now A) import without an error and B) get more accurate frame counts.

truncated gifs in the PIL renderer should now just either render the last frame over and over or rewind as soon as they hit a super problem

some borked file, not a borked OS hard drive access), and this was escalating up to the overall maintenance system, which was shutting down in panic. it turns out the PIL animated gif renderer we rarely use was raising overly serious errors on a truncated frame (i.e. fixed the false positive 'serious I/O Error! This is a significant hard drive problem' problems saw in last week's animated gif 'has transparency' rescanning.

Hydrus Network 537 download