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

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

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/efed6ba94a722c919d23241117fc4a44f2d06d8a ([wasm] Lazy-compilation: Fix patching of wasm-to-wasm wrappers).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs 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

Lowering priority (this requires "--wasm-lazy-compilation"). Also, no security implications.

ClusterFuzz has detected this issue as fixed in range 50497:50498.

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

Fuzzer: ochang_js_fuzzer
Job Type: linux_asan_d8_v8_mipsel_dbg
Platform Id: linux

Crash Type: DCHECK failure
Crash Address: 
Crash State:
  (lazy_callee) != nullptr in module-compiler.cc
  V8_Dcheck
  v8::internal::wasm::LazyCompilationOrchestrator::CompileLazyOnGCHeap
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_v8_mipsel_dbg&range=49708:49709
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_v8_mipsel_dbg&range=50497:50498

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

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

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