Predator and CL did not provide any possible suspects.
Using Code Search for the file, "pdfium_xfa_fuzzer" assigning to the concern owner.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/034ca9381180401b9b25eac088babf7fdae847d8

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

ClusterFuzz has detected this issue as fixed in range 463214:463222.

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

Fuzzer: libfuzzer_pdfium_xfa_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=463197:463214
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=463214:463222

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv94UCYNU6uO94p-BalGMHZTJFEgI7Jw4JC3xL_Cmbqfma3qfx5yggZ5dUWc9ItgZB1UDeXtTALd1pXqAqaCOsvUJ2vOo7ay6MiOZjtOCIDsImxpB1ROHF6y3koKDUh_dpfbBJ-4vbBi0MeOsJjLm8a_7Y7fPfuHUP_VoHWSd8GrDCTFnkXoK0hPCN6aFPEm5TGVaXZcXZfgWi7JEIx4oenBXFlk0LtSzH_s-KG5x4PoKX6OePpvo_L-S4s1yX-SCYLAbnhuydsVBsnhfgpIkqiQSdUyVm5Z9b_wJwAFYaNyhFPBAF47qetCdAz5d-XR563zciLW1939tjlpBm0e8kb5uQCldwAudLQIkI3Zsj33g0QrD2Os?testcase_id=4944959892619264


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

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

I'm guessing this is still an issue, re-opening so we can verify

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.