Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.
Thank You.

There's not really much here, just one way for the client to have the service allocate arbitrary amounts of memory (which it can do otherwise), using the debug markers API. It would be pretty easy to put a limit on that, both on the string size and the stack depth. I'll whip something up.

I don't think this is security sensitive (there are many other ways by which clients can get the GPU to goo OOM, at which point it'll abort and restart), so lowering priority.

ClusterFuzz has detected this issue as fixed in range 509853:509885.

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

Fuzzer: libFuzzer_gpu_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

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

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

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

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

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

WontFix since nothing was done to fix this.

 Issue 779348  has been merged into this issue.

 Issue 783927  has been merged into this issue.

 Issue 795657  has been merged into this issue.