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

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

I guess this is same with  issue 851913 , and somehow flaky.

ClusterFuzz has detected this issue as fixed in range 570347:570348.

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_ubsan_vptr_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !scope.AccessCheckFailed() in v8_dom_wrapper.cc
  blink::V8DOMWrapper::CreateWrapper
  blink::ScriptWrappable::Wrap
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=569660:569665
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=570347:570348

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

See https://github.com/google/clusterfuzz-tools 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 6360983153672192 is verified as fixed, so closing issue as verified.

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