ClusterFuzz has detected this issue as fixed in range 620892:620893.

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

Fuzzer: libFuzzer_v8_wasm_async_fuzzer
Fuzz target binary: v8_wasm_async_fuzzer
Job Type: x86_libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  v8_wasm_async_fuzzer
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=x86_libfuzzer_chrome_asan&range=620892:620893

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

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

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