New issue
Advanced search Search tips

Issue 828006 link

Starred by 1 user
Status: Duplicate
Merged: issue 847805
Owner: ----
Closed: Jun 2018
Cc:
scroggo@chromium.org
hcm@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Bus in SkPixmap::erase

Project Member Reported by ClusterFuzz, Apr 2 2018 
Detailed report: https://clusterfuzz.com/testcase?key=5668319605293056

Fuzzer: ochang_image_mutator
Job Type: linux_asan_chrome_mp
Platform Id: linux

Crash Type: Bus
Crash Address: 0x7f838f0aa000
Crash State:
  SkPixmap::erase
  SkBitmap::erase
  SkBitmap::eraseColor
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=523898:523900

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
Project Member

Comment 1 by ClusterFuzz, Apr 2 2018

Components: Internals>Skia
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

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

Comment 2 by hcm@chromium.org, Jun 12 2018

Cc: scroggo@chromium.org
Labels: -Pri-1 Pri-2
I'm not sure we have a problem to address here in Skia with corrupt/extraneous JPEG data being sent? cc Leon but thinking this may be won't fix

Comment 3 by hcm@chromium.org, Jun 12 2018

Cc: hcm@chromium.org

Comment 4 by scroggo@chromium.org, Jun 13 2018

Labels: ClusterFuzz-Ignore
Mergedinto: 847805
Status: Duplicate (was: Untriaged)
> corrupt/extraneous JPEG data being sent

Though the data is corrupt, the problem comes before we even see the bad data. The size is just too big (for this machine, at this particular time). The image is 8240 x 64544. At 4 bytes per pixel, this is over two gigs, raising our risk for overcommit.
►

Sign in to add a comment