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

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

> Unable to find actual suspect through code search and also observing no related changes under regression range.

> By comparing the stack trace of this issue, it looks similar to  bug 754120 , hence assigning to the same owner for more updates.

> keishi@ Could you please take a look in to this issue?

Thanks!

ClusterFuzz has detected this issue as fixed in range 583266:583305.

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

Fuzzer: libFuzzer_content_security_policy_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  pthread_key_init_np
  blink::ThreadState::Current
  unsigned char* blink::ThreadHeap::Allocate<blink::ContentSecurityPolicy>
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=547202:547312
Fixed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=583266:583305

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

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

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