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

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

Predator and CL could not provide any possible suspects.

Using Code Search for the file, "inline_flow_box.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/0e7d0d12eade3a80ef79e6c19a14bade77cc5b8e

mstensho@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

ClusterFuzz has detected this issue as fixed in range 573386:573395.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7ffebf519100
Crash State:
  blink::InlineFlowBox::PlaceBoxesInBlockDirection
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=573274:573280
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=573386:573395

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

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.