I'm trying to understand if an how an Isolate, and the Contexts within the 
Isolate, can be used after Isolate::TerminateExecution is called.
In v8.h, the documentation for Isolate::CancelTerminateExecution says:

Resume execution capability in the given isolate, whose execution
was previously forcefully terminated using TerminateExecution().
When execution is forcefully terminated using TerminateExecution(),
the isolate can not resume execution until all JavaScript frames
have propagated the uncatchable exception which is generated.  This
method allows the program embedding the engine to handle the
termination event and resume execution capability, even if
JavaScript frames remain on the stack.
This method can be used by any thread even if that thread has not
acquired the V8 lock with a Locker object.


It's not clear to me what this means for the Contexts that exist within the 
Isolate at the time TerminateExecution was called.
Does the terminate exception get raised in all Contexts within the Isolate?
Does the terminate exception only get raised in the current active Context?
After calling CancelTerminateExecution, can the existing Contexts still be 
used?

Thanks,
Chris

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to