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

Thanks!

ClusterFuzz testcase 6575752171225088 appears to be flaky, updating reproducibility label.

ClusterFuzz has detected this issue as fixed in range 615418:615419.

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

Fuzzer: bj_broddelwerk
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  font_platform_data in font_cache_skia.cc
  blink::FontCache::GetLastResortFallbackFont
  blink::FontFallbackList::GetFontData
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=523893:523905
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=615418:615419

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

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.