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:

canvas: Avoid unnecessary book-keeping of images in CanvasImageProvider. by khushalsagar@chromium.org - https://chromium.googlesource.com/chromium/src/+/cde9d1d1e464957716e4e15f44810fe28753e4df

[PE] Remove GetDocument() calls from a frequently used PaintInvalidator func. by vmpstr@chromium.org - https://chromium.googlesource.com/chromium/src/+/5e8d978cd7986057f1d9c7e05d6387b635cdfae6

Omit the parent LayoutView's scroll offset from FrameRect by szager@chromium.org - https://chromium.googlesource.com/chromium/src/+/cf91f7965c29e2bc93e81f79cef5d77481b00e6e

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

Duplicate of all the other blink::LowestCommonAncestor bugs?

I think LowestCommonAncestor is the stack trace that results when the paint property tree is badly-formed.  That might be a broad category of bugs, with a range of root causes, so I'm not sure it's correct to mark them as duplicates.  It may be better to leave them un-duped, so that bisecting is more accurate.

ClusterFuzz has detected this issue as fixed in range 538192:538205.

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

Fuzzer: miaubiz_svg_fuzzer
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000008
Crash State:
  blink::LowestCommonAncestor
  blink::PaintPropertyNode<blink::ClipPaintPropertyNode>::Changed
  blink::CompositedLayerRasterInvalidator::ChunkPropertiesChanged
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=537412:537498
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=538192:538205

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

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

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