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

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

This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Major regressions from https://chromium-review.googlesource.com/c/chromium/src/+/1102690, reverting.

ClusterFuzz has detected this issue as fixed in range 567913:567915.

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

Fuzzer: bj_broddelwerk
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Heap-use-after-free READ 8
Crash Address: 0x6110000444c0
Crash State:
  blink::LayoutBox::RemoveFloatingOrPositionedChildFromBlockLists
  blink::LayoutObjectChildList::RemoveChildNode
  blink::LayoutBlockFlow::RemoveChild
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=567913:567915

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

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.

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot