Routing some offline (really offline) discussion.
1) So afawk, on the Chrome side counters should be thread safe. Though,
there's
no way to access the data produced by the background threads, so it's
useless.
2) On the V8 side, the Counters class is not thread safe
3) Thus, background threads shouldn't muck with it (that is, the state after
this CL is more correct than before)
4) Counters contains other stuff like histogram timers which are definitely
not
thread safe.
5) The real fix to my problem (see bug) is on the Blink side anyway, so
this CL
is not super important.
This CL is by no means a long term solution and not strictly needed, but the
state of the world is still better after it than before.
https://codereview.chromium.org/716793002/
--
--
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.
