AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2014.05.01 20:49 "[Tiff] Inconsistencies in tiff library tool operation", by Prophet of the Way
2014.05.02 02:19 "Re: [Tiff] Inconsistencies in tiff library tool operation", by Bob Friesenhahn
2014.05.07 23:34 "Re: [Tiff] Inconsistencies in tiff library tool operation", by Prophet of the Way
2014.05.21 14:26 "Re: [Tiff] Inconsistencies in tiff library tool operation", by Bob Friesenhahn
2014.05.30 23:19 "Re: [Tiff] Inconsistencies in tiff library tool operation", by Prophet of the Way
2014.05.31 14:04 "Re: [Tiff] Inconsistencies in tiff library tool operation", by Bob Friesenhahn
2014.05.31 19:40 "Re: [Tiff] Inconsistencies in tiff library tool operation", by Bob Friesenhahn
2014.06.01 20:48 "Re: [Tiff] Inconsistencies in tiff library tool operation", by Prophet of the Way
2014.06.04 14:15 "Re: [Tiff] Inconsistencies in tiff library tool operation", by Bob Friesenhahn

2014.06.01 20:48 "Re: [Tiff] Inconsistencies in tiff library tool operation", by Prophet of the Way

It is important to take note of the zlib and libjpeg versions.

Zlib 1.2.3.X as delivered by Ubuntu Linux causes its own issues since the zlib maintainer thought that performance was more important than issues with consuming some unitialized data. Later zlib seems to be much better with this.

Modern IJG JPEG seems to be pretty good with valgrind but the Turbo JPEG variant uses SSE code/approaches which trigger valgrind complaints.

Thank you for telling me about this.

I used Zlib 1.2.5 and Turbo JPEG (libjpeg-turbo-1.2.0) for the above experiment. I'll try using IJG JPEG and will report the results. Please allow me some time.