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

Author: Mike Reed
Project: chromium-skia
Changelist: https://skia.googlesource.com/skia.git/+/b712089b93fadf3f3b560e9b21803f4c7626c94e
Time: Fri Apr 14 17:16:36 2017 -0400
Lines 287 of file SkBitmap.cpp which potentially caused crash are changed in this cl (frame #6, "SkBitmap::tryAllocPixels").
Minimum distance from crash line to modified line: 0. (file: SkBitmap.cpp, crashed on: 287, modified: 287).

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

ClusterFuzz has detected this issue as fixed in range 485950:486005.

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

Fuzzer: sugoi_filter_fuzzer
Job Type: linux_asan_filter_fuzz_stub
Platform Id: linux

Crash Type: Null-dereference WRITE
Crash Address: 0x000000000008
Crash State:
  SkAlphaThresholdFilterImpl::onFilterImage
  SkImageFilter::filterImage
  SkImageFilter::filterInput
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_filter_fuzz_stub&range=464815:464837
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_filter_fuzz_stub&range=485950:486005

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


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs 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 6572506510262272 is verified as fixed, so closing issue.

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