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

Author: vmpstr
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/70289fb699a311cf74de0853951145a90c35a5f5
Time: Thu Dec 01 02:33:05 2016
File picture_layer_impl.cc is changed in this cl (and is part of stack frame #4, "cc::PictureLayerImpl::UpdateRasterSource")
Minimum distance from crash line to modified line: 26. (file: picture_layer_impl.cc, crashed on: 607, modified: 581). 

Author: ericrk
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/1e323eedf1930d7fa26d21f25edbfeec6afea826
Time: Tue Dec 13 02:30:03 2016
File picture_layer_tiling.cc is changed in this cl (and is part of stack frame #1, "cc::PictureLayerTiling::ShouldCreateTileAt"; frame #2, "cc::PictureLayerTiling::CreateMissingTilesInLiveTilesRect")
Minimum distance from crash line to modified line: 34. (file: picture_layer_tiling.cc, crashed on: 125, modified: 159).

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

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

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

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

Crash Type: Float-cast-overflow
Crash Address: 
Crash State:
  gfx::ScaleToEnclosingRect
  cc::PictureLayerTiling::ShouldCreateTileAt
  cc::PictureLayerTiling::CreateMissingTilesInLiveTilesRect
  
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.31 Kb): https://cluster-fuzz.appspot.com/download/AMIfv965BLqrKmPm-GCtPb7vLgfl9Cu_7jhnYt53df4DwUylqHma6lmmPOEsyhhUa6-Hp8hIzPjDKUhxfhmqHMQ8VNjwjQnhTXjKt4M9UV2UYzSOSOVcQIVkJ5wzoB8k8tpnwrqo217ux3Tire9tLP8EfHc65-v5Ug?testcase_id=6002032675913728

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.

ClusterFuzz testcase 6002032675913728 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.