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

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

Unable to find actual suspect through code search and also observing no suspected CL's under regression range, hence adding appropriate label and requesting someone from blink team to look in to this issue.

Thanks!

ClusterFuzz has detected this issue as fixed in range 569793:569802.

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

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

Crash Type: CHECK failure
Crash Address: 
Crash State:
  flow_thread_offset.MightBeSaturated() || PageLogicalTopForOffset(flow_thread_off
  blink::LayoutMultiColumnSet::NextLogicalTopForUnbreakableContent
  blink::LayoutFlowThread::NextLogicalTopForUnbreakableContent
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=552767:552775
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=569793:569802

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

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 5200760636440576 is verified as fixed, so closing issue as verified.

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