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 let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

ClusterFuzz has detected this issue as fixed in range 52435:52436.

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

Fuzzer: ochang_js_fuzzer
Job Type: linux_ubsan_vptr_d8
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000030
Crash State:
  v8::internal::wasm::LazyCompilationOrchestrator::CompileDirectCall
  v8::internal::wasm::CompileLazy
  __RT_impl_Runtime_WasmCompileLazy
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=49708:49709
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=52435:52436

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

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

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