Removing owner to give predator a chance to auto-assign...

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/c7892d3577f53a707128bad7a392e05c2d904b60 ([wasm] Extract module compilation code into module-compiler.cc).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This check fails in a feature which is turned off by default at the moment. This is no release blocker.

No security implications.

ClusterFuzz has detected this issue as fixed in range 50604:50605.

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

Fuzzer: ochang_js_fuzzer
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: DCHECK failure
Crash Address: 
Crash State:
  Builtins::kWasmCompileLazy == code->builtin_index() in module-compiler.cc
  v8::internal::wasm::InstanceBuilder::LoadTableSegments
  v8::internal::wasm::InstanceBuilder::Build
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=45772:45773
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=50604:50605

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

See https://github.com/google/clusterfuzz-tools 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 4676063258214400 is verified as fixed, so closing issue as verified.

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