Assigning to the concern owner from Predator results --
The result is a list of CLs that change the crashed files. 

Author: thestig
Project: chromium-pdfium
Changelist: https://pdfium.googlesource.com/pdfium.git/+/fcf61b39ee597c73e80ba789833fb7fe49878422
Time: Thu Jun 09 18:29:35 2016 -0700
Lines 1850-1857, 1873-1877 of file fx_codec_progress.cpp which potentially caused crash are changed in this cl (frame #7, "CCodec_ProgressiveDecoder::StartDecode").
Minimum distance from crash line to modified line: 0. (file: fx_codec_progress.cpp, crashed on: 1850, modified: 1850).

@thestig -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

"Regressed" because we added the fuzzer.

ClusterFuzz has detected this issue as fixed in range 481576:482713.

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

Fuzzer: libFuzzer_pdf_codec_jpeg_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  pdf_codec_jpeg_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=398366:399171
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=481576:482713

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


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.

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

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

I don't see any reason for this to be resolved. Could it think it's resolved due to https://pdfium-review.googlesource.com/c/6552/?

For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md.

The link referenced in the description is no longer valid.

(bulk edit)

This image is 14895x17157. Given a sufficiently high memory limit it will complete, but the codec is behaving as expected.