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

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

Considering the above issue is related to V8, hence marking it as untriaged for more inputs.

Thanks!

assiging to cf sheriff for further investigation.

Looks like a broken build of the fuzzer binary.

ClusterFuzz has detected this issue as fixed in range 552758:552888.

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

Fuzzer: libFuzzer_v8_fully_instrumented_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

Crash Type: Ill
Crash Address: 0x000108ecd318
Crash State:
  v8::IsolateNewImpl
  Environment::Environment
  v8_fuzzer.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=536688:536853
Fixed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=552758:552888

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

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

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