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 blink team to look in to this issue.

Thanks!

ClusterFuzz has detected this issue as fixed in range 587950:587951.

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

Fuzzer: ochang_domfuzzer
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race READ 1
Crash Address: 0x562a2349ed58
Crash State:
  blink::FontDataCache::PurgeLeastRecentlyUsed
  blink::FontDataCache::Purge
  blink::FontCache::Invalidate
  
Sanitizer: thread (TSAN)

Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=587950:587951

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

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

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