FS#18397 - [libtiff/libjpeg] JPEG compression in TIFF segfaults

Attached to Project: Arch Linux
Opened by P.H. (Vain) - Friday, 19 February 2010, 11:05 GMT
Last edited by Allan McRae (Allan) - Tuesday, 02 March 2010, 03:22 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Eric Belanger (Snowman)
Allan McRae (Allan)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Using JPEG as compression inside a TIFF container is broken. As far as I can tell this was introduced with libjpeg-8.

I guess this is most probably an upstream bug but I'm still reporting it here fist because:

a) I'd like to know if other users are affected, too. I only know of few other persons who have seen this but the majority remains silent.

b) I don't know if this is a bug in libtiff, libjpeg or in any of the programs using those libraries.

c) I'm on i686 but I don't know if this applies to x86_64, too.

Package versions:

libtiff 3.9.2-2
libjpeg 8-2
imagemagick 6.5.9.5-1
xsane 0.997-2
sane 1.0.20-5
gimp 2.6.8-3

Steps to reproduce:

There's various ways to reproduce this. Most simple one:

$ scrot bla.jpg
$ convert bla.jpg bla.tiff

Backtrace from xsane (scanning and saving the image as TIFF with JPEG compression -- which is the default if you choose TIFF) is attached.

You could also try to save an image as TIFF with JPEG compression in GIMP. An old test program from the libtiff bugtracker also fails when it comes to JPEG compression:

http://bugzilla.maptools.org/show_bug.cgi?id=2097

Further references:

http://bbs.archlinux.org/viewtopic.php?id=90451
http://bbs.archlinux.org/viewtopic.php?pid=701430#p701430
http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=15509 (has this post been made by "our" Snowman?)
http://bugs.gentoo.org/show_bug.cgi?id=302789
   xsane-backtrace.log (3.8 KiB)
This task depends upon

Closed by  Allan McRae (Allan)
Tuesday, 02 March 2010, 03:22 GMT
Reason for closing:  Fixed
Additional comments about closing:  libjpeg 8.0.1-1
Comment by Eric Belanger (Snowman) - Friday, 19 February 2010, 15:23 GMT
FTR: Yes, I wrote the post on imagemagick.org forums. Now, I know the problem isn't with imagemagick but with libjpeg.
Comment by Allan McRae (Allan) - Friday, 19 February 2010, 15:46 GMT
I have sent an email describing this issue to the author of libjpeg.
Comment by P.H. (Vain) - Friday, 19 February 2010, 18:02 GMT
Alright, thank you! :)
Comment by Allan McRae (Allan) - Saturday, 20 February 2010, 00:19 GMT
The bug is known and the fix is on the way with v8a. The author expects the release to appear on 28-Feb.