Triggered by --validate-asm. Most likely a WontFix as it will be fixed by the new asm.js parser. I'll keep it open until I verified it is fixed.

ClusterFuzz has detected this issue as fixed in range 45077:45078.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_asan_d8_v8_arm_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  (func_type) != nullptr in asm-wasm-builder.cc
  
Sanitizer: address (ASAN)

Regressed: V8: 41371:41372
Fixed: V8: 45077:45078

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


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs 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 5567982010105856 is verified as fixed, so closing issue.

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

Yep, has been fixed by switching to new asm.js validator.