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

Author: Chris Dalton
Project: chromium-skia
Changelist: https://skia.googlesource.com/skia.git/+/febbffad1c24136f041d7fc2d5ffcd50e47a047f
Time: Thu Jun 08 13:12:02 2017 -0600
Lines 251-257, 266 of file SkPathOpsCubic.cpp which potentially caused crash are changed in this cl (frame #3, "SkDCubic::ComplexBreak"). 

Lines 574-603, 636-653, 665-668 of file SkGeometry.cpp which potentially caused crash are changed in this cl (frame #0, "normalize_t_s"; frame #1, "classify_cubic"; frame #2, "SkClassifyCubic").
Minimum distance from crash line to modified line: 0. (file: SkPathOpsCubic.cpp, crashed on: 257, modified: 257).

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

The assigned owner "csmartdalton@chromium.org" is not able to receive e-mails, please re-triage.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I am able to receive emails and these messages reached my inbox. I wonder why they thought it was bouncing?

Is someone able to help me understand what the fuzzer doesn't like this shift?

https://cs.chromium.org/chromium/src/third_party/skia/src/core/SkGeometry.cpp?type=cs&q=normalize_t_s+package:%5Echromium$&l=570

ClusterFuzz has detected this issue as fixed in range 478714:478793.

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

Fuzzer: libFuzzer_skia_pathop_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Undefined-shift
Crash Address: 
Crash State:
  normalize_t_s
  classify_cubic
  SkClassifyCubic
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=478353:478423
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=478714:478793

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


See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md 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 5820835683368960 is verified as fixed, so closing issue.

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