Download Latest Version libjpeg-turbo-2.0.90-vc64.exe (1.5 MB) Get Updates
Home / 2.0.3
Name Modified Size InfoDownloads / Week
Parent folder
libjpeg-turbo-2.0.3-gcc64.exe 2019-10-24 1.4 MB
libjpeg-turbo-2.0.3-gcc.exe 2019-10-24 1.2 MB
README.md 2019-10-24 2.4 kB
libjpeg-turbo-official_2.0.3_i386.deb 2019-09-05 1.1 MB
libjpeg-turbo-official_2.0.3_amd64.deb 2019-09-05 1.1 MB
libjpeg-turbo-official32_2.0.3_amd64.deb 2019-09-05 851.4 kB
libjpeg-turbo-official-2.0.3.x86_64.rpm 2019-09-05 1.1 MB
libjpeg-turbo-official-2.0.3.src.rpm 2019-09-05 2.2 MB
libjpeg-turbo-official-2.0.3.i386.rpm 2019-09-05 1.1 MB
libjpeg-turbo-2.0.3.tar.gz 2019-09-05 2.2 MB
libjpeg-turbo-2.0.3.tar.gz.sig 2019-09-05 65 Bytes
libjpeg-turbo-2.0.3.dmg 2019-09-05 11.8 MB
libjpeg-turbo-2.0.3-vc64.exe 2019-09-05 1.3 MB
libjpeg-turbo-2.0.3-vc.exe 2019-09-05 1.1 MB
libjpeg-turbo-2.0.3-jws.zip 2019-09-05 1.4 MB
Totals: 15 Items   27.8 MB 1,394

Package signatures

To ensure the integrity of the libjpeg-turbo binary packages, the RPM and DEB files and the source tarball are signed using the following key:
http://www.libjpeg-turbo.org/key/LJT-GPG-KEY-1024
http://pool.sks-keyservers.net/pks/lookup?op=get&search=0x85C7044E033FDE16
and the Windows installers are signed using a code signing certificate.

Packaging changes

  • New builds of libjpeg-turbo-2.0.3-gcc.exe and libjpeg-turbo-2.0.3-gcc64.exe were uploaded on 2019-10-23 to fix an issue whereby the libjpeg-turbo static libraries (libjpeg.a and libturbojpeg.a) could not be used with MinGW GCC v4-v6 toolchains.

2.0.3

Significant changes relative to 2.0.2:

  1. Fixed "using JNI after critical get" errors that occurred on Android platforms when passing invalid arguments to certain methods in the TurboJPEG Java API.

  2. Fixed a regression in the SIMD feature detection code, introduced by the AVX2 SIMD extensions (2.0 beta1[1]), that was known to cause an illegal instruction exception, in rare cases, on CPUs that lack support for CPUID leaf 07H (or on which the maximum CPUID leaf has been limited by way of a BIOS setting.)

  3. The 4:4:0 (h1v2) fancy (smooth) chroma upsampling algorithm in the decompressor now uses a similar bias pattern to that of the 4:2:2 (h2v1) fancy chroma upsampling algorithm, rounding up or down the upsampled result for alternate pixels rather than always rounding down. This ensures that, regardless of whether a 4:2:2 JPEG image is rotated or transposed prior to decompression (in the frequency domain) or after decompression (in the spatial domain), the final image will be similar.

  4. Fixed an integer overflow and subsequent segfault that occurred when attempting to compress or decompress images with more than 1 billion pixels using the TurboJPEG API.

  5. Fixed a regression introduced by 2.0 beta1[15] whereby attempting to generate a progressive JPEG image on an SSE2-capable CPU using a scan script containing one or more scans with lengths divisible by 16 would result in an error ("Missing Huffman code table entry") and an invalid JPEG image.

  6. Fixed an issue whereby tjDecodeYUV() and tjDecodeYUVPlanes() would throw an error ("Invalid progressive parameters") or a warning ("Inconsistent progression sequence") if passed a TurboJPEG instance that was previously used to decompress a progressive JPEG image.

Source: README.md, updated 2019-10-24