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

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

2nd bug with null read in clip path code, presumably SPv1.75.

ClusterFuzz has detected this issue as fixed in range 539400:539401.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000018
Crash State:
  blink::FragmentData::ClipPathProperties
  blink::ClipPathClipper::~ClipPathClipper
  ~OptionalBase
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=537453:537464
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=539400:539401

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

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

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