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

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

I don't see any reason to fix this.

ClusterFuzz has detected this issue as fixed in range 621472:621480.

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !std::isnan(static_cast<double>(value)) in math_extras.h
  float clampTo<float, double>
  blink::SVGLayoutSupport::CalculateScreenFontSizeScalingFactor
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=595703:595705
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=621472:621480

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

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.