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.

For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md.

The link referenced in the description is no longer valid.

ClusterFuzz has detected this issue as fixed in range 525196:525219.

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

Fuzzer: libFuzzer_v8_wasm_code_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=481600:482746
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=525196:525219

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

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.

ClusterFuzz testcase 6310779770109952 is verified as fixed, so closing issue as verified.

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