Issue metadata
Sign in to add a comment
|
V8 correctness failure in configs: x64,ignition:x64,ignition_turbo_opt |
||||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6293702455853056 Fuzzer: foozzie_js_mutation Job Type: v8_foozzie Platform Id: linux Crash Type: V8 correctness failure Crash Address: Crash State: configs: x64,ignition:x64,ignition_turbo_opt sources: 8e1 Sanitizer: address (ASAN) Regressed: V8: 44658:44659 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6293702455853056 Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Jun 10 2017
This is purely about the exception source position?
,
Jun 12 2017
,
Jun 14 2017
ClusterFuzz has detected this issue as fixed in range 45924:45925. Detailed report: https://clusterfuzz.com/testcase?key=6293702455853056 Fuzzer: foozzie_js_mutation Job Type: v8_foozzie Platform Id: linux Crash Type: V8 correctness failure Crash Address: Crash State: configs: x64,ignition:x64,ignition_turbo_opt sources: 8e1 Sanitizer: address (ASAN) Regressed: V8: 44658:44659 Fixed: V8: 45924:45925 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6293702455853056 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. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by danno@chromium.org
, Jun 10 2017Owner: jarin@chromium.org
Status: Assigned (was: Untriaged)