Status: Accepted
Owner: [email protected]
CC: [email protected], [email protected]
Labels: Type-Bug Priority-Medium
New issue 3143 by [email protected]: Bootstrapper and runtime/compiler
race on FLAG_track_double_fields
http://code.google.com/p/v8/issues/detail?id=3143
Flags are per-process. The bootstrapper uses a
NoTrackDoubleFieldsForSerializerScope which modifies the global
FLAG_track_double_fields by temporarily setting it to false, then restoring
it later. When another isolate is running in another thread in the same
process, it will observe "random" value changes of that flag.
I don't think the code reading that flag's value is engineered to assume
that the value might be non-constant. I haven't figured out a specific
failure scenario, but I strongly suspect this will create subtle
inconsistencies, such as code generated when the flag was off storing
immutable heap numbers into an object which other code (that was generated
when the flag was back on) will treat as mutable.
A possible workaround would be to copy the flag's value into the isolate,
so that new isolates starting up would not interfere with existing running
isolates' behavior.
--
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.
