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/+/88151691ad1b7388b29400a8ecf84ecc82fefcd1 (Only allocate a PaintLayerStackingNode if actually needed.).

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 571302:571304.

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

Fuzzer: mbarbella_webcomponents
Job Type: windows_asan_content_shell
Platform Id: windows

Crash Type: Heap-use-after-free READ 8
Crash Address: 0x122551683078
Crash State:
  blink::CompositingRequirementsUpdater::UpdateRecursive
  blink::CompositingRequirementsUpdater::UpdateRecursive
  blink::CompositingRequirementsUpdater::UpdateRecursive
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=570442:570453
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=571302:571304

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

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.

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot