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 adding ccs based on suspected regression changelists:

[wasm] Add checks and trace info for lazy compilation on native heap by kimanh@google.com - https://chromium.googlesource.com/v8/v8/+/f9d2c0daa36397d3a0f53dc5701bb5ae10aa7572

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Hooray, Kim's new checks caught a bug :)
We knew that there are bugs if the function table is exported and then modified, and that's exactly what the generated test case does.
Lowering priority, as this requires the '--wasm-lazy-compilation' runtime flag.
No security implications, as lazy compilation is disabled for wasm code.

ClusterFuzz has detected this issue as fixed in range 51426:51427.

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

Fuzzer: ochang_js_fuzzer
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: DCHECK failure
Crash Address: 
Crash State:
  Foreign::cast(exp_table->get(table_index))->foreign_address() == lazy_stub_or_co
  v8::internal::wasm::CompileLazy
  v8::internal::__RT_impl_Runtime_WasmCompileLazy
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=51170:51171
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=51426:51427

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

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

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