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

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

PTAL. It regressed 5 months ago but probably it's worth lookging given that the input is only 200 bytes long.

ClusterFuzz has detected this issue as fixed in range 572604:573026.

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

Fuzzer: libFuzzer_v8_wasm_compile_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  v8_wasm_compile_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=533015:533198
Fixed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=572604:573026

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

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.

ClusterFuzz testcase 5696975589343232 is verified as fixed, so closing issue as verified.

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