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 CL's under regression range, hence adding appropriate label and requesting someone from dev team to look in to this issue.

ClusterFuzz has detected this issue as fixed in range 581993:582026.

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

Fuzzer: libFuzzer_clear_site_data_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000020
Crash State:
  bool base::ContainsKey<std::__1::map<std::__1::basic_string<char, std::__1::char
  base::CommandLine::HasSwitch
  content::ClearSiteDataThrottle::ParseHeader
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=580747:580752
Fixed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=581993:582026

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

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

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