Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

For some reason Element::Clone() is called recursively.

After examining the testcase, it is similar to  crbug.com/745449  and the stack overflow is expected. The amount of node cloned is always growing and at some point will cause stack overflow.

ClusterFuzz testcase 5752328133804032 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

ClusterFuzz has detected this issue as fixed in range 543640:543641.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7ffc37827fe8
Crash State:
  find
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=523898:523900
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=543640:543641

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

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.