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 adding ccs based on suspected regression changelists:

Revert "Reduce the amount of padding needed for SDFs, take 2" by jvanverth@google.com - https://skia.googlesource.com/skia/+/825d4d798aed471ceff48fcb03667b268bc15a83

1010102, 101010x, 888x in sw by mtklein@chromium.org - https://skia.googlesource.com/skia/+/ac568a934f8f82bf3a359b757d67eb3a797d3593

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

I'm pretty sure it's not the revert.

Yeah, doesn't look like anything to do with 1010102/101010x/888x either.  Probably not a regression per-se.

ClusterFuzz has detected this issue as fixed in range 543289:543291.

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

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

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  SkCanvas::internalDrawDevice
  SkCanvas::internalRestore
  SkCanvas::restore
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=533136:533139
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=543289:543291

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

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

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