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/+/8c591c43c8d508412f44887b7d483003b7ce932b (Enable UBSan's pointer overflow check.).

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.

The CL in question enabled the check that found this, but isn't the right culprit. The pointer overflow here isn't interesting, this should just be a null deref.

ClusterFuzz has detected this issue as fixed in range 563530:563537.

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

Fuzzer: libFuzzer_skia_pathop_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Pointer-overflow
Crash Address: 
Crash State:
  SkOpEdgeBuilder::walk
  SkOpEdgeBuilder::finish
  OpDebug
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=551565:551569
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=563530:563537

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

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

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