The result is a list of CLs that change the crashed files. 

Author: sashab
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/5fcf8dbc81c32665ab015b7f0cf303f3427a3d93
Time: Mon Dec 05 04:39:40 2016
Lines 1143 of file LayoutBlockFlowLine.cpp which potentially caused crash are changed in this cl (frame #3, "blink::LayoutBlockFlow::layoutRunsAndFloatsInRange").
Minimum distance from crash line to modified line: 0. (file: LayoutBlockFlowLine.cpp, crashed on: 1143, modified: 1143).

This is just a rename, not related to this bug.

That regression range is huge. Can we get a narrower bisect?

Assigning to wangxianzhu@ in case the cause is https://chromium.googlesource.com/chromium/src/+/1ea99b023ae5c0d7a421b2e308fa910aa6bd107c.

It has no actual impact.

ClusterFuzz has detected this issue as fixed in range 440242:440280.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4719236271570944

Fuzzer: inferno_twister
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Float-cast-overflow
Crash Address: 
Crash State:
  blink::LineWidth::applyOverhang
  blink::BreakingContext::handleReplaced
  blink::LineBreaker::nextLineBreak
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=435261:438085
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=440242:440280

Minimized Testcase (0.18 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95HnUZ-tJVOOcnFGFo-F-HdCIE3lnZVP8OYgIJkMrGuk00i9q0MiZcQ1mgduFPL4Y18J7NmU4nRcGhUFOTyq8qmn2Sk_WLWkqjI0sL4Fd9ngeM2HZHKK6woJpwm2tMFY_D8u8uPPq9VcQwziCayhIIUhEEiow?testcase_id=4719236271570944

Additional requirements: Requires HTTP

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.