New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 850957 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Float-cast-overflow in blink::LayoutTableSection::DistributeExtraLogicalHeightToRows

Project Member Reported by ClusterFuzz, Jun 8 2018

Issue description

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

Fuzzer: inferno_twister
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Float-cast-overflow
Crash Address: 
Crash State:
  blink::LayoutTableSection::DistributeExtraLogicalHeightToRows
  blink::LayoutTable::DistributeExtraLogicalHeight
  blink::LayoutTable::UpdateLayout
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=552707:552711

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Project Member

Comment 1 by ClusterFuzz, Jun 8 2018

Components: Blink>Layout
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Cc: e...@chromium.org pnangunoori@chromium.org
Labels: M-68 Test-Predator-Wrong
Owner: robho...@gmail.com
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.
Using the code search for the file, “layout_table_section.cc and layout_table.cc” assigning to concern owner from GIT revision log.

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/d22a0616e628fe5e88618b288a98844b6891671c

@robhogan -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.

Also, CC'in the reviewer of the CL - eae@

Thank You.


Sign in to add a comment