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

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

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/0b4b14bc486c741a168182b5e7fa756fe8af58cd ([elements] Avoid NOP operation when shrinking HashTables).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

I can reproduce this with and without my change.

There was a wasm change committed in the same V8 roll as my change: https://chromium.googlesource.com/v8/v8/+log/98ce1809..e5661887

Perhaps more likely.

ClusterFuzz has detected this issue as fixed in range 558266:558270.

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

Fuzzer: libFuzzer_v8_wasm_compile_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  result_interpreter == result_turbofan in wasm-fuzzer-common.cc
  v8::internal::wasm::fuzzer::WasmExecutionFuzzer::FuzzWasmModule
  wasm-compile.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=557856:557860
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=558266:558270

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

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

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