Updates:
Status: Fixed
Comment #7 on issue 2885 by [email protected]: mksnapshot's output
isn't deterministic
http://code.google.com/p/v8/issues/detail?id=2885
The fix has landed as https://code.google.com/p/v8/source/detail?r=17473,
and https://code.google.com/p/v8/source/detail?r=17555 made a fixed random
seed the default. This way our builds are reproducible and we remove one
possible source of flakiness. If you want to get back the old randomized
behavior, use "make randomseed=0 ..." to build v8 or add v8_random_seed=0
to your GYP_DEFINES. (<= Hint for the node.js people!)
Just a note for the future: By handling hash tables explicitly in the
(de-)serializer, it would be possible to avoid baking the random seed into
the snapshot. Every deserialization could use a different seed then. This
would involve quite a bit of work and the added value seems to be rather
low, so we don't this for now.
--
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/groups/opt_out.
