V8 correctness failure in configs: x64,ignition_turbo_opt:x64,ignition_turbo_opt_eager |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4854349890322432 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:x64,ignition_turbo_opt_eager sources: 73b Sanitizer: address (ASAN) Regressed: V8: 43591:43592 Reproducer Testcase: https://clusterfuzz.com/download/AMIfv95L4lHUexJ5J7ypvhxIthqwLrRIjc-Ug4LaLlf9c0ur3mlzUTpas8RdICjrNJUJ4TIhkmogskl1XUZMEVqR2cG9fxM6tkjBWPRWM5Ih6liPLz_REdQ2SMuwfUBa-_EDqkWxpNyJRzn0Ik6m2zhFuLU_4N8FzdTJ-2fYok9g_ju-mEPQY76zoUeZwyePcvxgCjXnwV29f0djDMXsMRJgY91yx998WUU4cShZRPgB4F7Ka3j4X86SQIWQUm1dl9xgL2PsaWP2eiEh3cqLxUn-O29xn9rLlF2mVDuCtKgMQzVpvCcNpRSwheqdbEfyBZ6nZdkPljEXaauCYl2mZ6Bk_4FLyUVyOd96xG8QsWkbpUrghbYkDu0G9WZfANGfdWskwnw3Hfm5dzO2zj2TETLxjGMKa7cu-Q?testcase_id=4854349890322432 Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Mar 21 2017
Yup, this is the known case that PreParser doesn't find duplicates in arrow func param lists when the duplicates come from destructuring. (See e.g https://bugs.chromium.org/p/v8/issues/detail?id=6108 ) We'd probably want to suppress these cases. This is a probably simpler repro: function f() { (dup, {a: dup}) => {}; } Afaics the eval is not relevant.
,
May 16 2017
ClusterFuzz has detected this issue as fixed in range 45316:45317. Detailed report: https://clusterfuzz.com/testcase?key=4854349890322432 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:x64,ignition_turbo_opt_eager sources: 73b Sanitizer: address (ASAN) Regressed: V8: 43591:43592 Fixed: V8: 45316:45317 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4854349890322432 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.
,
May 16 2017
ClusterFuzz testcase 4854349890322432 is verified as fixed, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
May 16 2017
,
Sep 18 2017
We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.
,
Oct 19 2017
ClusterFuzz has detected this issue as fixed in range 48714:48715. Detailed report: https://clusterfuzz.com/testcase?key=4854349890322432 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:x64,ignition_turbo_opt_eager sources: 73b Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=43591:43592 Fixed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=48714:48715 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4854349890322432 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.
,
Oct 19 2017
,
Feb 24 2018
Removing v8-foozzie-failure label, because eager-lazy testing has been removed from correctness-fuzzer experiments. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by mstarzinger@chromium.org
, Mar 21 2017Owner: marja@chromium.org
Status: Assigned (was: Untriaged)
This is a difference between lazy and no-lazy parsing. The minimized version of the repro ... $ cat test/mjsunit/foo.js function f() { eval("(dup, {a: dup}) => {};"); } f(); The difference can be observed by running with these two command line flags: $ ./out/x64.debug/d8 test/mjsunit/foo.js $ ./out/x64.debug/d8 test/mjsunit/foo.js --no-lazy