Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically adding ccs based on suspected regression changelists:

handle failing pathop tests by caryclark@skia.org - https://skia.googlesource.com/skia/+/2587f41f2667b2add97f75583b71ebb74bc48af1

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Please assign to caryclark@google.com. As caryclark@skia.org, I cannot download the testcase or modify who this bug other than add this comment.

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

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

The following revision refers to this bug:
  https://skia.googlesource.com/skia/+/b64db38b854bd8f6d564b7741ebf4795d130d168

commit b64db38b854bd8f6d564b7741ebf4795d130d168
Author: Cary Clark <caryclark@skia.org>
Date: Thu Jul 26 12:04:17 2018

avoid uninitialized under fuzzer

https://skia-review.googlesource.com/143112
introduced new logic to handle failures;
fuzzer found a way to exploit this.

FWIW, skia's fuzzer did not call pathops when
fed the test case.

TBR=kjlubick@google.com

Bug:867314
Change-Id: Id894962d3f32e206362faff332a1330db75da175
Reviewed-on: https://skia-review.googlesource.com/143318
Reviewed-by: Cary Clark <caryclark@skia.org>
Commit-Queue: Cary Clark <caryclark@skia.org>
Auto-Submit: Cary Clark <caryclark@skia.org>

[modify] https://crrev.com/b64db38b854bd8f6d564b7741ebf4795d130d168/src/pathops/SkOpSegment.cpp

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/b709d48327c4af17ba3c31df66465f6f0f00b1d6

commit b709d48327c4af17ba3c31df66465f6f0f00b1d6
Author: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Thu Jul 26 16:25:01 2018

Roll src/third_party/skia f3ac64df1741..b5093bc9ede3 (3 commits)

https://skia.googlesource.com/skia.git/+log/f3ac64df1741..b5093bc9ede3


git log f3ac64df1741..b5093bc9ede3 --date=short --no-merges --format='%ad %ae %s'
2018-07-26 benjaminwagner@google.com [infra] Add Metal to no_upload.
2018-07-26 robertphillips@google.com Maybe fix numStencilBits TSAN crash
2018-07-26 caryclark@skia.org avoid uninitialized under fuzzer


Created with:
  gclient setdep -r src/third_party/skia@b5093bc9ede3

The AutoRoll server is located here: https://autoroll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel

BUG= chromium:867314 
TBR=benjaminwagner@chromium.org

Change-Id: I8b846218bf68424526b235de8dc3e9c415b76257
Reviewed-on: https://chromium-review.googlesource.com/1151212
Reviewed-by: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#578331}
[modify] https://crrev.com/b709d48327c4af17ba3c31df66465f6f0f00b1d6/DEPS

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

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

ClusterFuzz has detected this issue as fixed in range 578322:578337.

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

Fuzzer: libFuzzer_skia_pathop_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  SkOpAngle::lastMarked
  SkOpSegment::findNextOp
  bridgeOp
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=577670:577675
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=578322:578337

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

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