Issue metadata
Sign in to add a comment
|
V8 correctness failure in suppression: crbug.com/718739 |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5160760530698240 Fuzzer: foozzie_js_mutation Job Type: v8_foozzie Platform Id: linux Crash Type: V8 correctness failure Crash Address: Crash State: suppression: crbug.com/718739 Sanitizer: address (ASAN) Regressed: V8: 45316:45317 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5160760530698240 Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
May 22 2017
You can always just dedupe a suppression report into the original, e.g. see suppression crbug line. Clusterfuzz just creates a new bug as soon as something's suppressed.
,
Oct 19 2017
ClusterFuzz has detected this issue as fixed in range 48714:48715. Detailed report: https://clusterfuzz.com/testcase?key=5160760530698240 Fuzzer: foozzie_js_mutation Job Type: v8_foozzie Platform Id: linux Crash Type: V8 correctness failure Crash Address: Crash State: suppression: crbug.com/718739 Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=45316:45317 Fixed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=48714:48715 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5160760530698240 See https://github.com/google/clusterfuzz-tools for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by bmeu...@chromium.org
, May 16 2017Status: Assigned (was: Untriaged)