Issue metadata
Sign in to add a comment
|
Use-of-uninitialized-value in transform_scanline_bgrA |
||||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5709169819385856 Fuzzer: inferno_canvas_wrecker Job Type: linux_msan_chrome Platform Id: linux Crash Type: Use-of-uninitialized-value Crash Address: Crash State: transform_scanline_bgrA SkPngEncoder::onEncodeRows SkEncoder::encodeRows Sanitizer: memory (MSAN) Recommended Security Severity: Medium Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5709169819385856 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information. Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.
,
Mar 16 2018
,
Mar 17 2018
,
Mar 19 2018
,
Mar 19 2018
This was previously filed as issue 808875 . It looks like it's still not reproducible :( I've already looked through the stacktrace, and it's not obvious there's any problem in transform_scanline_bgrA, SkPngEncoder::onEncodeRows, or SkEncoder::encodeRows. It's possible that upstack our SkPixmap was not initialized properly, but I don't know enough about that code to make any guesses.
,
Mar 22 2018
,
Mar 22 2018
,
Aug 18
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ClusterFuzz
, Mar 16 2018Labels: Test-Predator-Auto-Components