Automatically assigning owner based on suspected regression changelist https://pdfium.googlesource.com/pdfium/+/826480cf599f61fe0366ab2bd5803dd53c9d0562 (Upgrade LibopenJPEG to 2.3).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

Aw another OpenJPEG problem. CJPX_Decoder::Init returns true (succeeds), and that's where all the time is being spent, which suggests we can't really do much about it. I could file a bug in their tracker?

I've filed https://github.com/uclouvain/openjpeg/issues/1122

Unassigning myself from the bug.

ClusterFuzz has detected this issue as fixed in range 609022:609029.

Detailed report: https://clusterfuzz.com/testcase?key=5761707100864512

Fuzzer: libFuzzer_pdf_jpx_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  pdf_jpx_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=510969:511009
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=609022:609029

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5761707100864512

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

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

ClusterFuzz testcase 5761707100864512 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.