Issue metadata
Sign in to add a comment
|
Crash in v8::internal::interpreter::BytecodeRegisterOptimizer::RegisterInfo::register_val |
||||||||||||||||||||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5527890074796032 Fuzzer: mbarbella_js_mutation Job Type: linux_asan_d8 Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x000000000000 Crash State: v8::internal::interpreter::BytecodeRegisterOptimizer::RegisterInfo::register_val v8::internal::interpreter::BytecodeRegisterOptimizer::OutputRegisterTransfer v8::internal::interpreter::BytecodeRegisterOptimizer::Materialize Regressed: V8: r33089:33090 Minimized Testcase (0.07 Kb): Download: https://cluster-fuzz.appspot.com/download/AMIfv97k_RmRTziLxsDxTUWM9e4sqPDEIKAeRHwRvQsLU7EJqKF4_0fET4NfgXHJwh--a7Qr7kvXqm6saqQbnQ-X9dZ7UdOpbqg4SZ-C7DyIDsq-Ezh3KQnKHqYQp6qT2DWKJglpJhXjEfy3CNbY65fw_iUt1gZiCA?testcase_id=5527890074796032 try { (y = 1[ [...[]]]) => 1; (y = 1[ [...[]]]) => {}; } catch(e) {; } Filer: tkonchada See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Jun 28 2016
This seems like a difference between between lazy and no-lazy. It repros with: d8 --no-lazy --allow-natives-syntax --ignition test.js But is fine without the --no-lazy.
,
Jun 28 2016
You might need to call the functions created by the arrow functions to trigger it without --no-lazy (since the functions won't be compiled until they are called).
,
Jun 28 2016
Yup, crashes without --no-lazy if you call the functions. This is probably a dup of issue 622663
,
Jun 28 2016
Yup, this is a dup of issue 622663 , the test case is the same. Nikolaos has a fix which should hopefully land soon.
,
Jun 29 2016
ClusterFuzz has detected this issue as fixed in range 37334:37335. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5527890074796032 Fuzzer: mbarbella_js_mutation Job Type: linux_asan_d8 Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x000000000000 Crash State: v8::internal::interpreter::BytecodeRegisterOptimizer::RegisterInfo::register_val v8::internal::interpreter::BytecodeRegisterOptimizer::OutputRegisterTransfer v8::internal::interpreter::BytecodeRegisterOptimizer::Materialize Regressed: V8: r33089:33090 Fixed: V8: r37334:37335 Minimized Testcase (0.07 Kb): Download: https://cluster-fuzz.appspot.com/download/AMIfv97k_RmRTziLxsDxTUWM9e4sqPDEIKAeRHwRvQsLU7EJqKF4_0fET4NfgXHJwh--a7Qr7kvXqm6saqQbnQ-X9dZ7UdOpbqg4SZ-C7DyIDsq-Ezh3KQnKHqYQp6qT2DWKJglpJhXjEfy3CNbY65fw_iUt1gZiCA?testcase_id=5527890074796032 try { (y = 1[ [...[]]]) => 1; (y = 1[ [...[]]]) => {}; } catch(e) {; } 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.
,
Nov 22 2016
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by tkonch...@chromium.org
, Jun 28 2016Labels: findit-wrong Te-Logged M-53
Owner: oth@chromium.org
Status: Assigned (was: Available)