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.

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

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

Just like in  Issue 842500 :

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:558275.

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

Fuzzer: afl_v8_wasm_code_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=557857:557863
Fixed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=558266:558275

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

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

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