[Bug 766010] jifmux fails to find EOI if it's not within the last 5 bytes

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=766010

--- Comment #5 from Mohammed Sameer <msameer at foolab.org> ---
(In reply to Thiago Sousa Santos from comment #4)
> Out of curiosity, was this file handcrafted or created by some device? I see
> it has 00 bytes padding at the end. Need to check if this is still
> considered a valid jpeg.

It was created by a device (Oneplus phone but not sure which one). It was
captured via android camera.

> How does this bug in jifmux affects you, other than the warning? I guess
> after your patch the resulting file should have the padding removed?

We use jifmux as part of our image capture pipeline for Sailfish OS. We get
jpeg images from android HAL and we need to "mux" additional exif tags.

When jifmux fails to parse the image, it also ignores any tags set by the
application. With the proposed patch the tags are muxed correctly.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.