Will take a look.
Could not easily reproduce locally, set's see if ClusterFuzz finds the same regression range again. Otherwise it's a WontFix.

ClusterFuzz has detected this issue as fixed in range 613538:613547.

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

Fuzzer: libFuzzer_v8_wasm_compile_fuzzer
Fuzz target binary: v8_wasm_compile_fuzzer
Job Type: windows_libfuzzer_chrome_asan
Platform Id: windows

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

Fixed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=613538:613547

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

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

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

The documentation for reproducing bugs on Windows was moved to: https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md