This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it.

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

Can you PTAL or assign this to someone who can? Thanks.

Looks like a duplicate of  crbug.com/675132 , which is fixed in Skia at https://skia-review.googlesource.com/c/6334/ -- that CL hasn't landed in Chrome quite yet. If that doesn't fix it, I'll look at this in more detail tomorrow

ClusterFuzz has detected this issue as fixed in range 439808:439935.

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

Fuzzer: libfuzzer_skia_pathop_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  SkOpContour::rayCheck
  SkOpSpan::sortableTop
  SkOpSegment::findSortableTop
  
Recommended Security Severity: Medium

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=439626:439695
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=439808:439935

Minimized Testcase (0.35 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97FKvCrLSCwbMmDHKSCI1XVzpK5Fr7hzpdf9xX4KvGlrYuaD5osEp45mjaUEpAhbRGfysvPybHXq5Izmc6WtaejE5aDWJ3sdNGxwdTP4drwtO9xEmccVtlVFMrL_bHOg863IyvKdxHeJsSh0z3Ybc_sePstuw?testcase_id=6705063054802944

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

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

This bug has been closed for more than 14 weeks. Removing security view restrictions.

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