Predator did not find any possible suspects.
Assigning to the concern owner from CL --
https://chromium.googlesource.com/chromium/src/+log/a737f9c91cf432640a454d51ffca2d398ef00c00..531f367559cc5168afc8ef2ce1219ecbcc9de2a8?pretty=fuller

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/d6f8a937c0d8fbfcbdfe7edc93255e454c5de3cf

@rune -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

My change should not affect stack use.

This is a stack overflow with an extremely deeply nested tree, and we're rebuilding/reattaching layout trees recursively.

ClusterFuzz has detected this issue as fixed in range 474922:474938.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Stack-overflow
Crash Address: 0x7fff51ff5e00
Crash State:
  blink::ContainerNode::AttachLayoutTree
  blink::Element::AttachLayoutTree
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=458620:458734
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=474922:474938

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


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.