Is the Google V8 engine really limited to 1 VM per process?

I can not get a direct answer to this. Is the Google V8 engine really limited to 1 VM per process?

If the google v8 engine is limited to only 1 virtual machine for each process, is this not an exception to use in libraries? Let's say I'm coding a C ++ library that uses a V8 called LibA. And someone else is encoding another library that uses a V8 called LibB. If the application contacts LibA and LibB, a bad thing will happen (right?).

I need a fast (with speed, which is the most important requirement actually) javascript parser for lib that I am trying to write, but I do not want to use v8 if I run into this problem (it is likely that the type of applications that reference it will also use v8 at some point).

+7
source share
1 answer

Based on this closed bug report , it is safe to say that the Google V8 engine is not limited to one thread for each process (starting around April 2011).

+3
source

All Articles