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

Author: drott
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/f2dc38825cce54c0b87841a420afbd71453d506b
Time: Thu Jan 19 11:28:10 2017
Lines 754 of file hb-ot-shape.cc which potentially caused crash are changed in this cl (frame #3, "hb_ot_position").
Minimum distance from crash line to modified line: 0. (file: hb-ot-shape.cc, crashed on: 754, modified: 754).

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

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

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

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

Fuzzer: inferno_twister
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  position_around_base
  position_cluster
  _hb_ot_shape_fallback_position
  
Sanitizer: undefined (UBSAN)

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

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

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.

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

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