On Thu, Feb 9, 2012 at 11:08 AM, Sturla Molden <sturla@molden.no> wrote:
On 09.02.2012 19:50, Masklinn wrote:
I don't think I've seen a serious refcounted JS implementation in the last decade. , although it is possible that JS runtimes have localized usage of references and reference-counted resources. AFAIK all modern JS runtimes are JITed which probably does not mesh well with refcounting.
In any case, V8 (Chrome's runtime) uses a stop-the-world generational GC for sure[0],
And Chrome uses one *process* for each tab, right? Is there a reason Chrome does not use one thread for each tab, such as security?
Stability and security. If something goes wrong/rogue, the effects are reasonably isolated to the individual tab in question. And they can use OS resource/privilege limiting APIs to lock down these processes as much as possible. Cheers, Chris