Integer-overflow in SkCoverageDeltaMask::convertCoverageToAlpha |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5889851976843264 Fuzzer: libFuzzer_skia_image_filter_proto_fuzzer Fuzz target binary: skia_image_filter_proto_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: Integer-overflow Crash Address: Crash State: SkCoverageDeltaMask::convertCoverageToAlpha SkBlitter::blitCoverageDeltas SkScan::DAAFillPath Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=602012:602024 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5889851976843264 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
,
Dec 17
Automatically adding ccs based on OWNERS file / target commit history. If this is incorrect, please add ClusterFuzz-Wrong label.
,
Dec 17
Automatically assigning owner based on suspected regression changelist https://skia.googlesource.com/skia/+/3dd116cdaa6117f95531df26c03994fe8b98e541 (SkEdgeBuilder refactoring). 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.
,
Jan 17
(5 days ago)
ClusterFuzz has detected this issue as fixed in range 623223:623224. Detailed report: https://clusterfuzz.com/testcase?key=5889851976843264 Fuzzer: libFuzzer_skia_image_filter_proto_fuzzer Fuzz target binary: skia_image_filter_proto_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: Integer-overflow Crash Address: Crash State: SkCoverageDeltaMask::convertCoverageToAlpha SkBlitter::blitCoverageDeltas SkScan::DAAFillPath Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=602012:602024 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=623223:623224 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5889851976843264 See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Jan 17
(5 days ago)
ClusterFuzz testcase 5889851976843264 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
, Dec 17Labels: Test-Predator-Auto-Components