You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We at work encountered segmentation faults, if the requested resolution on 16 bit JP2 resources is very high. I've played a little bit around with builds, one setup using the current head of the master branch (efcf57f), to work with the newer version of Kakadu, and Kakadu 8.2.1 and another one using the iipsrv 1.1 release and OpenJPEG 2.4.0. I created a few simple test images and it seems that the seg faults happen just with 16 bit JP2 files above a certain resolution, independent of the used JP2 library (see table). If we define a smaller supported size in the call, it works (e.g. /<testfile>/full/4500,5500/0/default.jpg).
Test call: /<testfile>/full/full/0/default.jpg
file
file size
width
height
channels
bits
raw size
success kdu
success opj
test01.jp2
2.8 KB
5000
7000
3
16
200.3 MB
yes
yes
test02.jp2
4.8 KB
8000
10000
3
16
457.8 MB
yes
yes
test03.jp2
6.8 KB
9000
11000
3
16
566.5 MB
no
no
test04.jp2
7.0 KB
10000
12000
3
16
686.6 MB
no
no
test05.jp2
11.1 KB
12000
16000
3
16
1098.6 MB
no
no
test06.jp2
8.9 KB
16500
22000
3
8
1038.6 MB
yes
yes
test07.jp2
11.8 KB
20000
25000
3
8
1430.5 MB
yes
yes
The text was updated successfully, but these errors were encountered:
This is probably a memory issue. What do you see in the iipsrv log file? If so, you should see a line which says "Error: Unable to allocate memory" for the images that don't work. The sizes are not so huge, so check whether you have any user memory limits set.
We at work encountered segmentation faults, if the requested resolution on 16 bit JP2 resources is very high. I've played a little bit around with builds, one setup using the current head of the master branch (efcf57f), to work with the newer version of Kakadu, and Kakadu 8.2.1 and another one using the iipsrv 1.1 release and OpenJPEG 2.4.0. I created a few simple test images and it seems that the seg faults happen just with 16 bit JP2 files above a certain resolution, independent of the used JP2 library (see table). If we define a smaller supported size in the call, it works (e.g. /<testfile>/full/4500,5500/0/default.jpg).
Test call: /<testfile>/full/full/0/default.jpg
The text was updated successfully, but these errors were encountered: