titzer could you help triage this please? Thanks!

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 is a crash in streaming compilation, which is turned off by default at the moment. This crash is not in production code.

ClusterFuzz has detected this issue as fixed in range 49379:49380.

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

Fuzzer: ochang_js_fuzzer_win
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: Heap-buffer-overflow WRITE {*}
Crash Address: 0x0b012fbb
Crash State:
  v8::internal::wasm::StreamingDecoder::Finish
  v8::internal::wasm::AsyncCompile
  v8::WebAssemblyCompile
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=49379:49380

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

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

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

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