Assigning to concern owner from Predator results --
The result is a list of CLs that change the crashed files. 

Author: mstensho
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/7a651c67dd9441867ff84657bd13e97df69bbe3f
Time: Fri Oct 14 19:24:22 2016
Lines 701-705 of file LayoutTable.cpp which potentially caused crash are changed in this cl (frame #3, "blink::LayoutTable::GetLayout").
Minimum distance from crash line to modified line: 0. (file: LayoutTable.cpp, crashed on: 701, modified: 701).

@mstensho -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

I don't feel responsible for this. Besides, are we really supposed to handle non-security integer overflows?

Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.

Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.
Thank You.

ClusterFuzz has detected this issue as fixed in range 551565:551568.

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

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

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  blink::LayoutTableSection::DistributeRemainingExtraLogicalHeight
  blink::LayoutTableSection::DistributeExtraLogicalHeightToRows
  blink::LayoutTable::DistributeExtraLogicalHeight
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=425398:425442
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=551565:551568

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

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.

 Issue 836662  has been merged into this issue.

ClusterFuzz testcase 5126523389214720 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

 Issue 836772  has been merged into this issue.