Description of problem:
openslide-write-png /home/christophe/Documents/Data/SVS/CB/CB2.svs 1000 1000 0 100 100 test.png
(process:12528): Openslide-CRITICAL **: Error decoding tile. Component 1 contains only 32768 blocks while component 0 has 65536 blocks
openslide-write-png: Error decoding tile. Component 1 contains only 32768 blocks while component 0 has 65536 blocks
Version-Release number of selected component (if applicable):
Steps to Reproduce:
works as expected with
Reassigning to openjpeg.
The OpenJPEG patch for CVE-2013-6045 disables decoding of images whose first color component has a higher resolution than subsequent components. This is a legitimate image encoding; consider, for example, YCbCr images with chroma subsampling. This change is preventing OpenSlide from decoding certain Aperio slide files (example slide at ).
For example, consider p0_06.j2k from the OpenJPEG test suite . With 1.3-9.el6_3:
$ j2k_to_image -i p0_06.j2k -o out.ppm
[INFO] tile 1 of 1
[INFO] - tiers-1 took 0.020997 s
[INFO] - dwt took 0.002000 s
[INFO] - tile decoded in 0.027995 s
PNM CONVERSION: Truncating component 0 from 12 bits to 8 bits
PNM CONVERSION: Truncating component 1 from 12 bits to 8 bits
PNM CONVERSION: Truncating component 2 from 12 bits to 8 bits
PNM CONVERSION: Truncating component 3 from 12 bits to 8 bits
Generated Outfile out.ppm
With 1.3-10.el6_5, the same command produces:
[INFO] tile 1 of 1
[ERROR] Error decoding tile. Component 1 contains only 33153 blocks while component 0 has 66177 blocks
ERROR -> j2k_to_image: failed to decode image!
The Debian bug has an ongoing discussion about this issue:
(In reply to Murray McAllister from comment #3)
> The Debian bug has an ongoing discussion about this issue:
I missed the "See Also". Sorry for the noise/duplicate
Debian has released updated packages that fix this problem:
The corrected patch is in the Debian bug.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.