Considering the above issue as v8 and leaving it as untriaged.

Note: Observing similar  issue 754428  with similar stack worked by @ahaas, hence cc'ing him for more updates on this issue.

Thanks!

The wasm fuzzer hangs in the start function, called during instantiate.
This is indeed related to 761784, but needs special handling since it's the start function which is running infinitely here.

ClusterFuzz has detected this issue as fixed in range 572608:573019.

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

Fuzzer: libFuzzer_v8_wasm_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  v8_wasm_fuzzer
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=449266:449283
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=572608:573019

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

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

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