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/+/553e70b9b2f36ce260f1e4d16c8d53aa154513a0 ([wasm] Merge function table and signature table).

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.

I explicitly uploaded this Clusterfuzz testcase ;)
It's not security relevant, since it requires the --no-wasm-jit-to-native flag.

ClusterFuzz has detected this issue as fixed in range 51199:51200.

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

Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: DCHECK failure
Crash Address: 
Crash State:
  obj->IsFixedArray() in wasm-objects-inl.h
  function_tables
  v8::internal::wasm::CreateModuleEnvFromCompiledModule
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=50622:50623
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=51199:51200

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

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

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

Setting severity-low for the sake of future reporting.

This bug has been closed for more than 14 weeks. Removing security view restrictions.

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