This issue looks similar to  bug 772751 , hence assigning to the same owner for more updates on this issue.

ahaas@ Could you please take a look in to this issue?

Thanks!

It looks like the fuzzer was able to build wasm code that contains an infinite loop.

ClusterFuzz has detected this issue as fixed in range 568748:568751.

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

Fuzzer: libFuzzer_v8_wasm_async_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=481147:481178
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=568748:568751

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

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.

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

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