CF points to dd65e4b837117205e2198b9765c333bab8fee1e4. PTAL

Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

This was fixed by relanding the CL.

ClusterFuzz has detected this issue as fixed in range 55248:55249.

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

Fuzzer: decoder_langfuzz
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  mem_size <= wasm::kV8MaxWasmMemoryBytes in wasm-objects.cc
  SetRawMemory
  v8::internal::SetInstanceMemory
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=55241:55242
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=55248:55249

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

See https://github.com/google/clusterfuzz-tools 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 5697725069524992 is verified as fixed, so closing issue as verified.

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

(found by multiple, including internal, fuzzers)

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot