-
Notifications
You must be signed in to change notification settings - Fork 456
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SIGSEGV in opj_j2k_update_image_data via pdfium_test #481
Comments
Reported by detonin on 2015-03-25 15:53:54
|
Reported by - _Attachment: [repro.jp2](https://storage.googleapis.com/google-code-attachments/openjpeg/issue-481/comment-2/repro.jp2)_ |
Reported by mayeut on 2015-06-03 20:53:57
|
Reported by mayeut on 2015-06-03 20:56:18 |
Should something be done to prevent decoding of 33GB images ? |
I was not able to retrieve the attachment (leads to 404 over here), so my comments may be inaccurate. However:
|
The attachment was not transferred because the issue was marked Restrict-View-Core-Team. I think I wasn't clear enough & this issue should probably be closed. Shall OpenJpeg provide (optional) mechanisms to prevent decoding "huge" images ? In the "normal" world, huge images are probably just corrupted images as this one where:
|
@mayeut I cannot find the flush_buffer on kdu_expand. It is present only in kdu_compress. Since kdu_expand has lot more options to control decompression (#quality, region size...), I guess this is not available directly. In any case kdu_expand should flush intermediate buffer (design of the lib) so memory consumption should not go up to 30Go as mentionned above (but again as you explained this is a different issue). I cant say much about the corrupted image. OpenJPEG as a library will do what's told. So at application level (PDF rendering) someone should maybe states: "hey, xsize=1049816 is far too big for me to render". 2cts |
OK, That's a valid answer to the question asked: "No, integrator shall check this on its own" |
Originally reported on Google Code with ID 481
Reported by
jun_fang@foxitsoftware.com
on 2015-03-15 18:02:39The text was updated successfully, but these errors were encountered: