ClusterFuzz has detected this testcase as flaky and is unable to reproduce it in the original crash revision. Skipping fixed testing check and marking it as potentially fixed.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4695709986586624

Fuzzer: libfuzzer_pdf_jpx_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  opj_tcd_dc_level_shift_decode
  opj_tcd_decode_tile
  opj_j2k_decode_tile
  

Minimized Testcase (0.30 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95vjljudfaDz1B_Sf4bCq3mEQy8jEICWkrF-55LFDwRlWXmvRUf1MX1jYLK-vk-ouDYe9BXb9cmk5Phsb-Fbxsk-OZvgrbZRX1FrXeN3MV6pbirHYCUrzjit1G10ySKWgRy--10U3Dm5P32w-jhbMPolN8xIQ?testcase_id=4695709986586624

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

As per comment#3, closing this issue.
Thank you.