Marking this issue as Wont Fix as it is an Out of Memory issue.

Thank You.

Re-opening the issue, as it has been incorrectly closed as WontFix. Out of Memory issues are valid bugs in most of the cases.

WontFix status might be assigned only by the owner of the target code, if there is no way or no reason to prevent fuzzer from causing OOM crash.

Sometimes we mark OOMs found with MSan as WontFix because MSan has big memory overhead. However, that should not be done without a proper understanding of the target as well as without looking at the crash stats.

As per the  Issue 668857  owner, assigning this issue to @cwallez.
@cwallez -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thanks.

Thanks for the report.

This failures are caused by the shader having HUGE arrays and the translator trying to make an AST to initialize all elements. Closing as won't fix.

ClusterFuzz testcase 5633568117358592 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

ClusterFuzz has detected this issue as fixed in range 517395:517523.

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

Fuzzer: libFuzzer_angle_translator_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  angle_translator_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=497217:497277
Fixed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=517395:517523

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.