Thanks Jakob.
As I'm an embedder, and when I need to terminate execution, it's when I
need to throw a retry-able exception to my system and start from scratch.
So I'm following the practice Ben suggested a while ago, which seems to
work with some basic testing:
v8::V8::TerminateExecution(iso
Generated code doesn't check for termination requests after every machine
instruction, because that would be way too slow. It does check in loops
(not on every iteration, though, only now and then), and some other
situations like function calls.
Note that TerminateExecution is intended for permane
Is this 64bit? If so it could be this issue:
http://code.google.com/p/v8/issues/detail?id=1180
I only observed this issue with stack overflows but the root cause is that
stack limits are not being set correctly so perhaps they're related? Try
this.. right after you enter the context in your new th
Hi Ravi,
would you provide a reduced test case that reproduces this issue? Without
that I can only guess. Exception termination takes place by throwing
uncatchable exceptions. However, when terminating execution we have to
return control to C++ frames on the stack. When that happens the embedder
s
