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/+/c7a0755ef5b59863b714ceaa988a57c882195f86 (Search correctly for inline ancestors without a sibling when dirtying lineboxes).

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.

+mstensho who reviewed https://chromium.googlesource.com/chromium/src/+/c7a0755ef5b59863b714ceaa988a57c882195f86

ClusterFuzz has detected this issue as fixed in range 569222:569223.

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

Job Type: linux_asan_chrome_mp
Platform Id: linux

Crash Type: Heap-use-after-free READ 8
Crash Address: 0x612000052d18
Crash State:
  blink::FloatingObject::Create
  blink::LayoutBlockFlow::InsertFloatingObject
  blink::LayoutBlockFlow::LinkToEndLineIfNeeded
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=465674:465716
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=569222:569223

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

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