Predator and CL could not provide any possible suspects.
Using the code search for the file, “SkPixmap.cpp” assigning to concern owner from GIT blame.

Suspecting Commit#
https://skia.googlesource.com/skia.git/+/78663f9dad1235e47c2fa9cfd1a9dd979d373871

@herb -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.

Also, CC'ing the reviewer of the above CL - fmalita@

Thank You.

It looks like the BMP decode produced dubious data.

The image in question is 31,232 x 16,385. At 4 bytes per pixel, that's 2,046,945,280 bytes, or approximately 2 gigs.

erase attempts to set all of those bytes to 0 in one pass.

Chromium will display this file, though it is slow to load/render.

We've seen other issues of attempting to allocate too much memory leading to failure. See issue 820889 and issue 813489.

Deleted: bad.bmp 586 bytes

bad.bmp 586 bytes Download

ClusterFuzz testcase 4876145833803776 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

 Issue 828006  has been merged into this issue.

ClusterFuzz has detected this issue as fixed in range 604477:604485.

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

Fuzzer: noel-image-flip
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Bus
Crash Address: 0x7f2841a66000
Crash State:
  __msan_memset
  SkPixmap::erase
  SkBitmap::erase
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=535692:535694
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=604477:604485

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

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.