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

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

ClusterFuzz has detected this issue as fixed in range 525196:525217.

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

Fuzzer: libFuzzer_v8_fully_instrumented_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Null-dereference WRITE
Crash Address: 0x000000000000
Crash State:
  v8::internal::JSTypedArray::MaterializeArrayBuffer
  v8::internal::Builtin_Impl_TypedArrayPrototypeBuffer
  v8::internal::Builtin_TypedArrayPrototypeBuffer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=517645:517681
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=525196:525217

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

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

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