Issue metadata
Sign in to add a comment
|
V8 correctness failure in configs: x64,ignition_turbo_opt:ia32,ignition_turbo_opt |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6666629357502464 Fuzzer: foozzie_js_mutation Job Type: v8_foozzie Platform Id: linux Crash Type: V8 correctness failure Crash Address: Crash State: configs: x64,ignition_turbo_opt:ia32,ignition_turbo_opt sources: a44 Sanitizer: address (ASAN) Regressed: V8: 46837:46838 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6666629357502464 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Jul 27 2017
The repro here looks strange. Should try it out.
,
Aug 1 2017
ClusterFuzz has detected this issue as fixed in range 47006:47007. Detailed report: https://clusterfuzz.com/testcase?key=6666629357502464 Fuzzer: foozzie_js_mutation Job Type: v8_foozzie Platform Id: linux Crash Type: V8 correctness failure Crash Address: Crash State: configs: x64,ignition_turbo_opt:ia32,ignition_turbo_opt sources: a44 Sanitizer: address (ASAN) Regressed: V8: 46837:46838 Fixed: V8: 47006:47007 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6666629357502464 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.
,
Nov 16
Seems to get into a rangeerror and now properly crashes. This is indeed fixed. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by machenb...@chromium.org
, Jul 27 2017Status: Duplicate (was: Untriaged)