Predator and CL did not provide any possible suspects.
Using Code Search for the file, "pdf_codec_icc_fuzzer" assigning to the concern owner who might be related to the issue.

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

upstream has some new patches for oss-fuzz, don't know helpful or not, though.

ClusterFuzz has detected this issue as fixed in range 464315:464333.

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

Fuzzer: libfuzzer_pdf_codec_icc_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=464294:464315
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=464315:464333

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv955MooPRF_GYIPoNWXEO9kVxvVjA8ldcl3P2Tif3zC3UJbv6KrliZUFNmfmb1jqHqUoVaRv7_9yfZEx5kf0Dmo3WoJlH8L2xqJ_qZkvG0uIo6LiowPvp9TkIEnnQqAG0hvgxXid6qQokoqc8TiVS2ohLJEKaPp6qcUkQJ0ImmZtSPscqk8lRvXpVtXygeOSbP4uMT_4F9roZJz1u4fjwxGkhHZ6IFcG99WosadLF6A7DgEmaIbOKbGmVhMfhjcBcCb9tdBhzaMMqydB5YbDHo1jg0un7AoXCVYuJgUrUEvBZkpE9AGwMgUJ383uK8fgUJSVIIPuYlF9AcO71_K-zk-trIwSqdCAAC3NOTw7siwBvJNcV9w?testcase_id=4704159665487872


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

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

I don't think this would have been fixed, we should 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.