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

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

Predator and CL could not provide any possible suspects.
Using the code search for the file, “scoped_refptr.h” assigning to concern owner.
Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/78b1544ced9e7e98a805c3f34087ccaefa93cb31


tzik@ -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thank You.

ClusterFuzz has detected this issue as fixed in range 514924:514966.

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

Fuzzer: libFuzzer_feature_policy_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  ptr_ in scoped_refptr.h
  scoped_refptr<blink::SecurityOrigin>::operator->
  _start
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=514313:514360
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=514924:514966

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

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

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