Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5711726810234880 Fuzzer: ifratric-browserfuzzer-v3 Job Type: linux_asan_chrome_v8_arm Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x00000000 Crash State: SkAAClipBlitter::blitH SkAAClipBlitter::blitRect antifilldot8 Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_v8_arm&range=413791:414128 Minimized Testcase (0.44 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96XzO7jSP7WGsaY2BIu3y5MRIVhvTj8PLISa3nmM1vlD6DBLAiCWkTcySVFypfj0L5QN49vxxuXI2gRBQM29iIzKTZn9s8GQo_Ae2A4OqTLB2dKTyiHvIa0XtmLXiySfj3bNtnvUlsqAfvVdrlbj9w9IYQDvQjYgXPthS5LL7cI-sL_j4jang9RxNUg59kbaCRfCRRf7sEbMY6bw9Nj0TGhnB5RLn5_sUcfOoxAFhuW31Ddi20TBi9MmnW3HIkb7OIUBwPV7yU-yAI279spNXCIBhgD-oTtZs1W1YbvkdNZuOT6zk_b_2VQ_oYvGarCTYD-N3gyhYqtaCcE36g1ctGCo5_-ZwQDAkZ8aF5LPDLsEnZAWR0?testcase_id=5711726810234880 Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
bsalomon@, could you please look into this change (https://chromium.googlesource.com/skia/+/19fe41e85e6ce3e78b3a69fce1cf28edf937027d) if possible? Thank you!
That change is to an unrelated part of the code. Assigning to reed@ for investigation or further delegation.
ClusterFuzz has detected this issue as fixed in range 454873:455052. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5711726810234880 Fuzzer: ifratric-browserfuzzer-v3 Job Type: linux_asan_chrome_v8_arm Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x00000000 Crash State: SkAAClipBlitter::blitH SkAAClipBlitter::blitRect antifilldot8 Sanitizer: address (ASAN) Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_v8_arm&range=413791:414128 Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_v8_arm&range=454873:455052 Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv96XzO7jSP7WGsaY2BIu3y5MRIVhvTj8PLISa3nmM1vlD6DBLAiCWkTcySVFypfj0L5QN49vxxuXI2gRBQM29iIzKTZn9s8GQo_Ae2A4OqTLB2dKTyiHvIa0XtmLXiySfj3bNtnvUlsqAfvVdrlbj9w9IYQDvQjYgXPthS5LL7cI-sL_j4jang9RxNUg59kbaCRfCRRf7sEbMY6bw9Nj0TGhnB5RLn5_sUcfOoxAFhuW31Ddi20TBi9MmnW3HIkb7OIUBwPV7yU-yAI279spNXCIBhgD-oTtZs1W1YbvkdNZuOT6zk_b_2VQ_oYvGarCTYD-N3gyhYqtaCcE36g1ctGCo5_-ZwQDAkZ8aF5LPDLsEnZAWR0?testcase_id=5711726810234880 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.
ClusterFuzz testcase 5711726810234880 is verified as fixed, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Comment 1 by msrchandra@chromium.org
, Jan 2 2017