Regression CL ::
https://chromium.googlesource.com/chromium/src/+log/3bf4c3c36d1d2fa3a477287b66a0c559ed1ddfa7..b89e2a2a5560d3bc5909c1cf7a3aed5446680489?pretty=fuller

Skia CL ::
https://chromium.googlesource.com/skia/+log/7600183ba7d8c8df6fbba1b32a73e6394216754e..844a0b425741f07cb233332405143931586bbb7d?pretty=fuller

Possible suspect from the above skia roll
https://codereview.chromium.org/1430593007

mtklein@ Could you please look into this issue if it is related to your change,else please route this to an appropriate owner for this issue.

Thanks,

Looks like the same as 623669.

We've also seen this in 626980, where calloc is not involved.  We see the same problem through both SkMallocPixelRef::NewAllocate and SkMallocPixelRef::NewZeroed.

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

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

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

Fuzzer: sugoi_filter_fuzzer
Job Type: linux_asan_filter_fuzz_stub_32bit
Platform Id: linux

Crash Type: Null-dereference WRITE
Crash Address: 0x00000004
Crash State:
  SkPixelRef::SkPixelRef
  SkMallocPixelRef::MakeZeroed
  SkSpecialSurface::MakeRaster
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_filter_fuzz_stub_32bit&range=357565:358520
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_filter_fuzz_stub_32bit&range=485950:486007

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


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.