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: Brian Osman
Project: chromium-skia
Changelist: https://skia.googlesource.com/skia.git/+/61624f0c716b576706659750d87b6956f4c15722
Time: Fri Dec 09 14:51:59 2016 -0500
Lines 252 of file SkDevice.cpp which potentially caused crash are changed in this cl (frame #4, "SkBaseDevice::drawImageRect"). 

File SkBitmapDevice.cpp is changed in this cl (and is part of stack frame #3, "SkBitmapDevice::drawBitmapRect")
Minimum distance from crash line to modified line: 0. (file: SkDevice.cpp, crashed on: 252, modified: 252).

@Brian Osman -- 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=5888086136586240

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

Crash Type: Float-cast-overflow
Crash Address: 
Crash State:
  SkRect::round
  SkTreatAsSprite
  SkDraw::drawBitmap
  
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.70 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94pkKe38-RIzzIl19rlomUeTcvi2A_gWQzOGxOW1sZ_CfkbmQd5o5YSW7GYCR5nQpQM4pxYlAN5GQJ2X_poOoQfCAS7dGqwn_xwtdYEPGYndtUPsv763vSjUMso-3UdNaWETQeLhHeIMUB5gwi-TIgR_30IdQ?testcase_id=5888086136586240

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 5888086136586240 is verified as fixed, so closing issue.

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