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

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

Unable to find actual suspect through code search nor from the provided regression range. This issue looks similar to  Issue 813411 , hence cc'ing to the same dev for more updates on this issue.

Thanks!

This doesn't seem super important to fix right now given other priorities. The failing test case is some horrendous mess of DOM manipulation. 

ClusterFuzz has detected this issue as fixed in range 538518:538530.

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

Fuzzer: miaubiz_svg_fuzzer
Job Type: linux_ubsan_vptr_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000048
Crash State:
  blink::LayoutSVGContainer::Paint
  blink::SVGContainerPainter::Paint
  blink::LayoutSVGContainer::Paint
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=537471:537478
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=538518:538530

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

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.