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

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

Multi-return fuzzer issue. Andreas, can you take a look?

ClusterFuzz has detected this issue as fixed in range 536089:536096.

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

Fuzzer: afl_v8_multi_return_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  v8::internal::Code::CopyFrom
  v8::internal::Heap::AllocateCode
  v8::internal::Factory::NewCode
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=533277:533284
Fixed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=536089:536096

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

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.