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/+/6f2cdb6210cd7c04edad9c1f857ac3039f2b4abe (Inline Node::RareData.).

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.

This test just creates an infinite DOM tree which eventually runs out of stack space during layout.

Please don't "WONTFIX" unless the bug is actually fixed.

kochi@, could you triage?

Ah, the test creates an infinite DOM tree, closing makes sense.

ClusterFuzz has detected this issue as fixed in range 568005:568006.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_chrome_mp
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7ffede146db8
Crash State:
  blink::Element::RecalcStyleForReattach
  blink::ContainerNode::RecalcDescendantStylesForReattach
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=543307:543308
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=568005:568006

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

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.