Status: New
Owner: ----
New issue 3520 by [email protected]: Chrome JS on MacOSX array push
bug, pushing NaN sometimes results in INT MIN being pushed leading to
erratic client code behavior.
http://code.google.com/p/v8/issues/detail?id=3520
This is a test case for a chrome browser javascript bug.
http://jsfiddle.net/113dpmgx/
In Chrome version 36.0.1985.143 on Mac OS X 10.8.5
The bug is :
Pushing NaN into arrays will sometimes end up as INT MIN
instead of NaN in the array.
This does not happen for other values even 'null'.
This is a big issue because client code that expects a pushed NaN
to stay as NaN, will break. It happens to our app.
Also noticed that this bug is non-deterministic (appears so) in
how/when it would happen. And when it does, it could happen for
subsequent array push NaN operations and eventually subside.
Thought it was an array realloc issue but after discussion in another
chrome group,
seems most likely to be an optimization issue as the bug is reproducible
without Chrome dev tools, but does not show with dev tools.
Run this a few times and you will notice varying output with errors.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
