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

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

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/70ae6f206f33968e8a94a894f01534247c8d210f ([LayoutNG] Reduce memory usage for NGBaseline).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

drott@, can you take a look? Does this help tracking issue 561873?

ClusterFuzz has detected this issue as fixed in range 622450:622452.

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

Fuzzer: puzzor
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=604942:604945
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=622450:622452

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 5690996175929344 is verified as fixed, so closing issue as verified.

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