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/+/bb4692c0babd2fdd7f54e6f4f876a6e060d9bb8a (Convert V0 UA shadow in <object> and <embed> to use V1).

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.

My CL doesn't touch the part in the stack trace, I am innocent :)

It looks the stack overflow is happening while detaching layout for
plugin elements.  I'm not sure they are really nested very deep, or
looping due to a bug.

ClusterFuzz has detected this issue as fixed in range 559423:559424.

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

Fuzzer: inferno_twister
Job Type: linux_lsan_chrome_mp
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=528905:528906
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=559423:559424

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

Additional requirements: Requires HTTP

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.

ClusterFuzz testcase 4921493889482752 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.