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

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

npm@ do you have time to look at a font issue?

No time, going OOO pretty soon. If the stacktrace is correct, this looks like a Mac bug that should be reported to Apple.

ClusterFuzz has detected this issue as fixed in range 583266:583305.

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

Fuzzer: libFuzzer_pdf_font_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

Crash Type: Floating-point-exception
Crash Address: 
Crash State:
  TSFNTFont::GetVariationAxes
  TFPFont::TFPFont
  TFPInMemoryFont::TFPInMemoryFont
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=472872:472906
Fixed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=583266:583305

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

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

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