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

Thank You.

Given that this is an OOM related to the swiftshader fuzzer, suspecting the swiftshader roll in the regression range:


https://chromium.googlesource.com/chromium/src/+/ed09b0b2296674b3aadeac11ca33475a809d2d8c

sugoi@, can you take a look? Thanks!

1) I temporarily reverted some code related to that change yesterday, so it's possible that clusterfuzz will mark this as fixed soon (not certain).
2) I'll re-enable this soon and I'll investigate this issue when I do, but given that this change enables OpenGL ES 3.0 (as opposed to OpenGL ES 2.0, currently), a whole new set of formats becomes available, increasing the chances of creating extremely large textures (1Gb or more per texture). When this happens, an out-of-memory error is likely and is the proper behavior in that case.

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

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

Fuzzer: libFuzzer_gpu_swiftshader_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=495516:495531
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=509885:509914

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

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

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