Null-dereference READ in SkDiscardableMemory::Create |
|||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5402216944107520 Fuzzer: libFuzzer_paint_op_buffer_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000000 Crash State: SkDiscardableMemory::Create SkBitmapCache::Alloc SkSpecialImage_Gpu::onGetROPixels Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=527343:527370 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5402216944107520 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Jan 16 2018
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
Apr 10 2018
,
Apr 10 2018
,
Apr 13 2018
,
Apr 13 2018
,
Apr 15 2018
ClusterFuzz has detected this issue as fixed in range 550790:550813. Detailed report: https://clusterfuzz.com/testcase?key=5402216944107520 Fuzzer: libFuzzer_paint_op_buffer_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000000 Crash State: SkDiscardableMemory::Create SkBitmapCache::Alloc SkSpecialImage_Gpu::onGetROPixels Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=527343:527370 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=550790:550813 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5402216944107520 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Apr 15 2018
ClusterFuzz testcase 5402216944107520 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ClusterFuzz
, Jan 16 2018