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

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

Forwarding this to Geoff that is working on the passthrough commandbuffer that this fuzzer tests.

ClusterFuzz has detected this issue as fixed in range 466873:466895.

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

Fuzzer: libfuzzer_gpu_angle_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=450717:450741
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=466873:466895

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


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

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