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 assigning owner based on suspected regression changelist https://skia.googlesource.com/skia/+/2dc50cc92af008155d98f3729828eae71f82930d (add conservative bounds to raster tiling).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

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

commit bdf985c7614f0d4ec8214fe28fa464b6b202b163
Author: Mike Reed <reed@google.com>
Date: Mon Jun 25 16:17:15 2018

remove bad assert

Bug:  855854 
Change-Id: Ifad8fd1f89000b206de39ef261a99292ee63b7a1
Reviewed-on: https://skia-review.googlesource.com/137383
Reviewed-by: Mike Reed <reed@google.com>
Commit-Queue: Mike Reed <reed@google.com>

[modify] https://crrev.com/bdf985c7614f0d4ec8214fe28fa464b6b202b163/src/core/SkBitmapDevice.cpp

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

commit 96722ce99416f1e4ffd0a4bd8c043000ce76b69f
Author: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Mon Jun 25 20:50:33 2018

Roll src/third_party/skia ed55419d859b..ff168d9258e0 (4 commits)

https://skia.googlesource.com/skia.git/+log/ed55419d859b..ff168d9258e0


git log ed55419d859b..ff168d9258e0 --date=short --no-merges --format='%ad %ae %s'
2018-06-25 bsalomon@google.com Put GrPrimitiveProcessor/GrGeometryProcessor before GrPipeline in param lists.
2018-06-25 enne@chromium.org Validate transformed SkPaintImageFilter rects
2018-06-25 hcm@google.com update externally published milestone schedule
2018-06-25 reed@google.com remove bad assert


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

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: 852048,chromium:855854
TBR=jcgregorio@chromium.org

Change-Id: I66cbf0f9efc9793ac60c1d969b4ad7207eea857e
Reviewed-on: https://chromium-review.googlesource.com/1113825
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@{#570170}
[modify] https://crrev.com/96722ce99416f1e4ffd0a4bd8c043000ce76b69f/DEPS

ClusterFuzz has detected this issue as fixed in range 570168:570172.

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

Fuzzer: inferno_canvas_wrecker
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900000001
Crash State:
  SkBitmapDevice::drawBitmap
  SkBitmapDevice::drawBitmap
  SkBitmapDevice::drawBitmapRect
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=550732:550739
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=570168:570172

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

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

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