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

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

Looks like infinite recursion in shadow dom tear-down.

Looks very similar to

https://bugs.chromium.org/p/chromium/issues/detail?id=847056
https://bugs.chromium.org/p/chromium/issues/detail?id=846495

We should check if this repros after they are fixed.

I will take this one.

This is not a recent regression and lowering priority.

ClusterFuzz has detected this issue as fixed in range 567635:567636.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7fffad40cef8
Crash State:
  VectorBufferBase
  VectorBuffer
  Vector
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=562324:562330
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=567635:567636

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

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.