As this is an Out-of-memory related issue, assuming this can be changed to Won't Fix.
Adding related Devs in Cc who might be related.
Thank You.

ClusterFuzz has detected this issue as fixed in range 467861:467917.

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

Fuzzer: libfuzzer_pdf_fm2js_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  pdf_fm2js_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=467799:467861
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=467861:467917

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


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 5683281782898688 is verified as fixed, so closing issue.

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

We have been trying to track these down as they block the fuzzer from progressing. It's possible there is a solution we can do in code depending on what is happening.

Bulk-WontFixing these bugs. This was a bug on ClusterFuzz side, see bug 717534. We will start seeing new testcases auto-filed in a day or two. We can't leave these open as ClusterFuzz won't autoverify them after ClusterFuzz-Wrong label.

We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.