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

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

ClusterFuzz has detected this issue as fixed in range 619954:619955.

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

Fuzzer: libFuzzer_v8_wasm_code_fuzzer
Fuzz target binary: v8_wasm_code_fuzzer
Job Type: x86_libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Ill
Crash Address: 0xf7fa7930
Crash State:
  v8::internal::wasm::fuzzer::WasmExecutionFuzzer::FuzzWasmModule
  wasm-code.cc
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=x86_libfuzzer_chrome_asan&range=619954:619955

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

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

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

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