Timeout in skia_pathop_fuzzer |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6289797567217664 Fuzzer: libFuzzer_skia_pathop_fuzzer Job Type: mac_libfuzzer_chrome_asan Platform Id: mac Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: skia_pathop_fuzzer Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6289797567217664 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. If the fix resolved the issue, please close the bug by marking as Fixed. Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Aug 11 2017
,
Aug 17 2017
Stack-overflow, Out of memory and Timeout issues are 'P2'.
,
Aug 23 2017
,
Sep 6 2017
The following revision refers to this bug: https://skia.googlesource.com/skia/+/38702ab43b2857f2fe06afb8dad1339d76a2fd84 commit 38702ab43b2857f2fe06afb8dad1339d76a2fd84 Author: Cary Clark <caryclark@skia.org> Date: Wed Sep 06 14:40:18 2017 possible fix for pathops timeout fuzzer causes pathops to loop somewhere finding complex intersections, but does not have a reproducible test case. Somewhat grasping at straws, the failing condition in this CL was triggered by the fuzzer tests, but may or may not be related to the hang. TBR=reed@google.com Bug: 754434 Change-Id: Ia8edc0709cec559b277ed83a5ad6feb67d8088c6 Reviewed-on: https://skia-review.googlesource.com/42780 Reviewed-by: Cary Clark <caryclark@skia.org> Commit-Queue: Cary Clark <caryclark@skia.org> [modify] https://crrev.com/38702ab43b2857f2fe06afb8dad1339d76a2fd84/tests/PathOpsOpTest.cpp [modify] https://crrev.com/38702ab43b2857f2fe06afb8dad1339d76a2fd84/src/pathops/SkPathOpsTSect.h
,
Sep 11 2017
Since it's not readily reproducible, don't know for sure that it's fixed, but will assume it is until told otherwise |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ClusterFuzz
, Aug 10 2017