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 CL's under regression range, hence adding appropriate label and requesting someone from dev team to look in to this issue.

With reference to  Issue 866870 , cc'ing eae@ for further triage

Thanks!

It will probably take a day just to reduce that testcase, so given the current priority, I won't spend any time on it.

ClusterFuzz has detected this issue as fixed in range 583970:583971.

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

Fuzzer: puzzor
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  IsFirstAfterBreak(line_top_in_flow_thread) || !line.PaginationStrut() || !IsLogi
  blink::MinimumSpaceShortageFinder::ExamineLine
  blink::ColumnBalancer::TraverseLines
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=576352:576359
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=583970:583971

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

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

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