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

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

Bisects to c2aaf0a6fa659a8f41b778f3fca039ba62a32e74.

Yes, that CL already got reverted (https://crrev.com/c/1360633), fixed and relanded (https://crrev.com/c/1361040). Should be fixed, waiting for ClusterFuzz to verify.

ClusterFuzz has detected this issue as fixed in range 613540:613541.

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

Fuzzer: libFuzzer_v8_wasm_compile_fuzzer
Fuzz target binary: v8_wasm_compile_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=613048:613052
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=613540:613541

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

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

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