Based on the issue "631564".

@caryclark: Could you please look into this issue.

Else, suspecting:

Author: caryclark
Project: chromium-skia
Changelist: https://chromium.googlesource.com/skia.git/+/55888e44171ffd48b591d19256884a969fe4da17
Time: Mon Jul 18 17:01:36 2016
Lines 384 of file SkOpSpan.cpp which potentially caused crash are changed in this cl (frame #2, "SkOpSpan::insertCoincidence").

Lines 523-545 of file SkPathOpsCommon.cpp which potentially caused crash are changed in this cl (frame #4, "HandleCoincidence").

Lines 312, 322 of file SkPathOpsOp.cpp which potentially caused crash are changed in this cl (frame #5, "OpDebug").

Lines 1382-1417 of file SkOpCoincidence.cpp which potentially caused crash are changed in this cl (frame #3, "SkOpCoincidence::mark").

File SkOpBuilder.cpp is changed in this cl (and is part of stack frame #6, "SkOpBuilder::resolve")
Minimum distance from crash line to modified line: 0. (file: SkOpSpan.cpp, crashed on: 384, modified: 384).

Thank you.

I'm away on vacation. I'll be back August 8th.

ClusterFuzz has detected this issue as fixed in range 408608:408631.

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

Fuzzer: libfuzzer_skia_pathop_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000000
Crash State:
  segment
  containsCoincidence
  SkOpSpan::insertCoincidence
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=405990:406128
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=408608:408631

Minimized Testcase (0.43 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96ibU2_GkeIMhDKzYJJ5tGK-JsvFjMQJ91Yr45Q2mcpHLNum4I9XcDSgWRAf8pK_cjcIQglWplu2wS3UJ6RUs7UxpwJVLOZ_JCqeP_mqoLrxhG5mPOg82MhcJPXT3Xbau3T6V6C8C0FPIG75mlY_d-o_wmRaQ?testcase_id=6004649790537728

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

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

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

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