Issue 528 in webp: Can't process jpeg file

[anton… via monorail]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 528 by anton...@gmail.com: Can't process jpeg file
https://bugs.chromium.org/p/webp/issues/detail?id=528

$cwebp ./743990_mainViewOtherLot.jpg -o ./743990_mainViewOtherLot.webp

libjpeg error: Input file read error
Error! Could not process file ./743990_mainViewOtherLot.jpg
Error! Cannot read input picture file './743990_mainViewOtherLot.jpg'

$ cwebp -version
1.2.0

OS: macOS and Linux Centos

Attachments:
743990_mainViewOtherLot.jpg 8.0 KB

--
You received this message because:
1. The project was configured to send all issue notifications to this address

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

[jz… via monorail]

Comment #1 on issue 528 by jz...@google.com: Can't process jpeg file
https://bugs.chromium.org/p/webp/issues/detail?id=528#c1

Thanks for the report. The webp tools rely on libjpeg to process the file. It looks like the image may be truncated.

djpeg reports an error:
$ djpeg 743990_mainViewOtherLot.jpg >out.ppm
Premature end of JPEG file

So does ImageMagick:
$ convert 743990_mainViewOtherLot.jpg out.png
convert-im6.q16: Premature end of JPEG file `743990_mainViewOtherLot.jpg' @ warning/jpeg.c/JPEGWarningHandler/389.
convert-im6.q16: Corrupt JPEG data: premature end of data segment `743990_mainViewOtherLot.jpg' @ warning/jpeg.c/JPEGWarningHandler/389

Chrome renders a portion of the image and the others do as well, though they return error codes themselves. cwebp expects to be able to read the whole image and will fail otherwise.