Comment #9 on issue 2874 by [email protected]: Threading problems in
test-api
http://code.google.com/p/v8/issues/detail?id=2874
Please correct me if I'm wrong but Isolate is supposed to be used on a
single thread at any point in time and hence there is always a current
thread (may be null) for an isolate - the thread where Isolate::Current()
will return that isolate.
With the current implementation the signal handler first takes current
isolate from TLS and after that in order to get current thread specific
simulator instance for the isolate it has to call
v8::internal::Isolate::FindPerThreadDataForThread which will go through the
list of all PerIsolateThreadData. I believe the latter step can be
eliminated by storing current PerIsolateThreadData in a field on isolate
when entering that isolate on a given thread. Am I missing something?
--
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.
