Integer-overflow in blink::LayoutTableCell::ComputeIntrinsicPadding |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5361810589614080 Fuzzer: ifratric-browserfuzzer-v3 Job Type: linux_ubsan_chrome Platform Id: linux Crash Type: Integer-overflow Crash Address: Crash State: blink::LayoutTableCell::ComputeIntrinsicPadding blink::LayoutTableSection::LayoutRows blink::LayoutTable::UpdateLayout Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=523880:523906 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5361810589614080 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
May 16 2018
Predator and CL could not provide any possible suspects. Using the code search for the file, “layout_table_cell.cc or layout_table_section.cc” assigning to concern owner from GIT blame. Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/2ae783af6398cb95a5bd45c2f70754f5c9bbf85c @joysyu / @eae -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes. Thank You.
,
May 25 2018
,
Jun 1 2018
ClusterFuzz testcase 5361810589614080 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. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, May 16 2018Labels: Test-Predator-Auto-Components