We have a command-line tool to reproduce this crash locally (on Goobuntu) from chromium source code with a single command. It'd really help speed up the development process. The tool is in alpha. Ping tanin@ or everestmz@ if you are interested.

ClusterFuzz has detected this issue as fixed in range 452786:452819.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5145840470720512

Fuzzer: libfuzzer_v8_wasm_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x000001e71618
Crash State:
  v8::internal::wasm::WasmFullDecoder::DefaultValue
  v8::internal::wasm::WasmFullDecoder::InitSsaEnv
  v8::internal::wasm::WasmFullDecoder::Decode
  
Sanitizer: address (ASAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=451962:452004
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=452786:452819

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv95hJN3wDN7EpmWm25ZCaJmu73m6r8yclf9ZASI-0NktRAuV1fgidffcepiDUhI72RwdDQBfwmB4bLRgiY8dx4et1qMh7PZ_-FWut0jTqscmBV2S2HBqlgfFfAeIZfGjuXc7JCR2UOyX1y_lJRaD8FWHN2LyZCElY0BR6e6omc70iwyxsZ7qH9DV7zUmAa6U_voy7154PHR_hmmyEmM41r6itwz3KPVn5JGTTx6RWaqGQ74nv-dMM8TE49ZXMYujis1ffUEnjFZCN7J6eFtzDedd_k-xojYqo02UtBfpOsHnxT-gQcjRfYz-gAjSkgrgd2H3bHp80gzyoLBDC4JL0FFNfyPDtzb7QmHsft34lOXg9ELweMMa8ub48CqINvYMnvtxgCkjMQ7ChN8hkynWff6Y0WJCDQ?testcase_id=5145840470720512


See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.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 5145840470720512 is verified as fixed, so closing issue.

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