Lowering priority, as this requires --wasm-interpret-all (might also be possible to reproduce by setting breakpoints).

 Issue 744312  has been merged into this issue.

ClusterFuzz has detected this issue as fixed in range 47230:47231.

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

Fuzzer: inferno_js_fuzzer
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  Code::WASM_TO_JS_FUNCTION == code->kind() in wasm-interpreter.cc
  v8::internal::wasm::ThreadImpl::CallCodeObject
  CallImportedFunction
  
Sanitizer: address (ASAN)

Regressed: V8: 44058:44059
Fixed: V8: 47230:47231

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


See https://github.com/google/clusterfuzz-tools 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 5225351847608320 is verified as fixed, so closing issue as verified.

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

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot