Closed masom closed 9 years ago
Another gif with a bad last frame:
OK. Fixed in bd093162f884856e9c13bb0fa8ac7cfd6a1ac133.
I just built https://github.com/kohler/gifsicle/commit/bd093162f884856e9c13bb0fa8ac7cfd6a1ac133 and gifsicle still produces the following error:
gifsicle:fail_gifsicle.gif:#102: read error: missing 52926 pixels of image data
gisicle --help
does show --no-ignore-errors Quit on very erroneous input GIFs.
Despite the error, the GIF was still processed this time. Right?
On Wed, Mar 25, 2015 at 10:05 AM, Martin Samson notifications@github.com wrote:
I just built bd09316 https://github.com/kohler/gifsicle/commit/bd093162f884856e9c13bb0fa8ac7cfd6a1ac133 and gifsicle still produces the following error:
gifsicle:fail_gifsicle.gif:#102: read error: missing 52926 pixels of image data
gisicle --help does show --no-ignore-errors Quit on very erroneous input GIFs.
— Reply to this email directly or view it on GitHub https://github.com/kohler/gifsicle/issues/35#issuecomment-86042994.
Oh my bad. I didn't realize the message saying the output was STDOUT on a terminal. The gif was generated properly with the warnings
Thank you!
This error can be ignored? Then continue to convert?
Gifsicle crashes when a gif contains an invalid/corrupted frame.
A command line switch to tell gifsicle to drop corrupted frames would be awesome.
ImageMagick has the same problem:
Not including the specific frame that is corrupted works:
convert 'fail_gifsicle.gif[0-101]' -coalesce test.gif
Gif: