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:

[cleanup] Make {AreAliased} generic and variadic by clemensh@chromium.org - https://chromium.googlesource.com/v8/v8/+/70f2bd0d1418e0290baa37cb62641132ada3edc4

[wasm] Add WasmFeatures to enable/detect features by titzer@chromium.org - https://chromium.googlesource.com/v8/v8/+/6aa2a253136d8d3d987c7fb8b3bc68208a5a532c

If this is incorrect, please let us know why 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

titzer: Assigning to you since it looks like crrev.com/c/1163670 made some changes to function-body-decoder and it is in the regression range. Can you take a look? (And reassign if appropriate?) Thanks.

ClusterFuzz has detected this issue as fixed in range 584760:584761.

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

Fuzzer: libFuzzer_v8_wasm_async_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: DCHECK failure
Crash Address: 
Crash State:
  pc <= end_ in decoder.h
  int v8::internal::wasm::Decoder::read_leb_tail<int,
  v8::internal::wasm::BlockTypeImmediate<
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=583006:583013
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=584760:584761

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

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