New issue
Advanced search Search tips

Issue 703119 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Crash in SkImage_Base::SkImage_Base

Project Member Reported by ClusterFuzz, Mar 20 2017

Issue description

Components: Internals>Skia
Labels: Test-Predator-Wrong-CLs M-58

Comment 2 by hcm@chromium.org, Mar 28 2017

Labels: -Reproducible
Owner: hcm@chromium.org
I'm having a hard time getting precise data out of CF on this one- the regression results are invalid, the latest stack is completely different from the original.  I'm redoing the tests to see what we get..will maintain ownership for now until we get better data or close.
Project Member

Comment 3 by ClusterFuzz, Apr 15 2017

ClusterFuzz has detected this issue as fixed in range 464815:464837.

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

Fuzzer: sugoi_filter_fuzzer
Job Type: linux_asan_filter_fuzz_stub_32bit
Platform Id: linux

Crash Type: UNKNOWN WRITE
Crash Address: 0x00000004
Crash State:
  SkImage_Base::SkImage_Base
  sk_sp<SkImage_Raster> sk_make_sp<SkImage_Raster, SkBitmap const&, bool>
  SkMakeImageFromRasterBitmap
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_filter_fuzz_stub_32bit&range=450347:450401
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_filter_fuzz_stub_32bit&range=464815:464837

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv95cEFvLhOhc6yfeYo2C3Z6pJhjGuf2GpO3gmqJJlxNOr1zxY3f_CSA3p3KvgAKtKJ0G0wWSKaaD_ZlPx1hObxNUbN5xMoYrWkeh9c2sIPAcz0XUAFNNsBKhYsUmUJt5YrL2-vaGaOGSQstPHbWiD2chmFDipi4CUV9wvL6KhEucQuVW2Dz7k_FM0WktfFxvmOo6-eiAHu5cvVdQArftCrqsWOQJtYUL_1Qot23lxu1MpbUfqqkr_92lg1glghQTC4_bU0z-8E3jQDladc5mbfdCPoXLsicC7WmQTNtPF_6L1Drm5RUj0zGhLPKfsMNMODe1MUVVV-NWovvqoZM7Q7wIDet2OlXC8qjgFa_U4EAALJG3dMbe5hNHuZDKZ3EUDkoV2cdqwmRt9Z9FvKkOkEVnGXr74A?testcase_id=5162483460603904


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.
Project Member

Comment 4 by ClusterFuzz, Apr 15 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Untriaged)
ClusterFuzz testcase 5162483460603904 is verified as fixed, so closing issue.

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

Sign in to add a comment