Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/a9be49beca9893711aad3ffac2e00132d38c3bf8 (Optimize out work in CompositingLayerAssigner).

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.

ClusterFuzz has detected this issue as fixed in range 573113:573114.

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

Fuzzer: marty_html_twiddler
Job Type: windows_asan_content_shell
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  layer->GetCompositingReasons() || (layer->GetCompositingState() != kNotComposite
  blink::CompositingLayerAssigner::AssignLayersToBackingsInternal
  blink::CompositingLayerAssigner::AssignLayersToBackingsInternal
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=570320:570321
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=573113:573114

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

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.