Predator and CL did not provide any possible suspects.
Using Code Search for the file, "pdf_codec_tiff_fuzzer" assigning to the concern owner.

@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 465516:465534.

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

Fuzzer: libfuzzer_pdf_codec_tiff_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  pdf_codec_tiff_fuzzer
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=465497:465516
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=465516:465534

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv963NgqhHM5lwg40Ak6pmhXuAorGr12SYZWGTq01pueYwg2aoyFaaKd1XKRiStUZZ_zeRUg4lCoalsmBHUWOCot6nTzWAzbbZRuFGY9xRR02q39Hpd4F6o48l7KO6AW1Xmo5qLrURsSSlWF6xsjZxmOVzsXAnlgN_Z9LcKU2rVfcUKahuDaOTv11XAGqc28EsqvKNb48bJ2i2tD1xQvC9QscAkfxNYWpN74hc8wD0f6LOSKeCGnlLj_dExFOlPQRf4GRRpsxJs6W7c8KGyzeyFfaJt7VsYZBXw2arlKryrR1Jps2W7GFQt5adqXR7ypRnXI4je9L8f1nB4WqVzV-FnhxL6W6pXzXi7kDo4V2IDYnaDwye5I?testcase_id=6012407777591296


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

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

I don't believe you my fuzzy friend.

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.