This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

Requires --wasm-interpret-all, will lower priority. Also, no security implications.

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

Fuzzer: inferno_js_fuzzer
Job Type: linux_asan_d8
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  deopt_data->get(1)->ToInt32(&index) in wasm-interpreter.cc
  v8::internal::wasm::UnwrapWasmToJSWrapper
  v8::internal::wasm::ThreadImpl::CallExternalJSFunction
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8&range=47909:47910

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

See https://github.com/google/clusterfuzz-tools for more information.

Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.

ClusterFuzz has detected this issue as fixed in range 48580:48581.

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

Fuzzer: inferno_js_fuzzer
Job Type: linux_asan_d8
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  deopt_data->get(1)->ToInt32(&index) in wasm-interpreter.cc
  v8::internal::wasm::UnwrapWasmToJSWrapper
  v8::internal::wasm::ThreadImpl::CallExternalJSFunction
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8&range=47909:47910
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8&range=48580:48581

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

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 has detected this issue as fixed in range 48580:48581.

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

Fuzzer: inferno_js_fuzzer
Job Type: linux_ubsan_vptr_d8
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  deopt_data->get(1)->ToInt32(&index) in wasm-interpreter.cc
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=47909:47910
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=48580:48581

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

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

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