ClusterFuzz has detected this issue as fixed in range 515138:515154.

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

Fuzzer: libFuzzer_v8_wasm_code_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  interpreter != liftoff (ffffff40 vs 2); WasmCodeFuzzerHash=417c3dee in wasm-fuzz
  v8::internal::wasm::fuzzer::WasmExecutionFuzzer::FuzzWasmModule
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=514357:514376
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=515138:515154

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

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.

This is *not* a dupe of 728820, so it seems to be the second bug found by the fuzzer :)

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

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