Null-dereference READ in blink::BaseRenderingContext2D::ShouldDrawImageAntialiased |
||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5449485979353088 Fuzzer: jesse_avalanche Job Type: linux_msan_chrome Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000000 Crash State: blink::BaseRenderingContext2D::ShouldDrawImageAntialiased blink::BaseRenderingContext2D::DrawImageInternal blink::BaseRenderingContext2D::drawImage Sanitizer: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=567394:567406 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5449485979353088 Issue filed automatically. See https://www.chromium.org/developers/testing/memorysanitizer#TOC-Reproducing-ClusterFuzz-Bugs for instructions to reproduce this bug locally.
,
Jan 19
(3 days ago)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/3589d51340c2aec28922e156e6f6b033b5a75998 (Add a Shared Memory variant of CanvasResourceProvider). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged. |
||
►
Sign in to add a comment |
||
Comment 1 by ClusterFuzz
, Jan 19 (3 days ago)Labels: Test-Predator-Auto-Components