Status: New
Owner: ----
New issue 3777 by [email protected]: v8 never cleans up after terminated
threads
https://code.google.com/p/v8/issues/detail?id=3777
After using v8 once in a thread there remains persistent data in the
isolate until that isolate is completely destroyed. This creates
performance penalties while using v8 in environments where many threads are
quickly created and destroyed. A thread pool mitigates the problem, but is
not a robust solution.
A quick confirmation of the issue can be confirmed by greping v8 trunk for
`thread_data_table_`. There are several references to `Insert`, `Lookup`,
and one reference to `RemoveAllThreads`.. but no references at all to
`Remove`.
Attached is a very short application which demonstrates the loss of
performance.
Attachments:
thread-data.cc 746 bytes
--
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.
