Catching out-of-memory situation in V8 without invalidating entire Isolate

[Ivan P.]

I'm using V8 3.19 in my application. I will need to upgrade soon to some latest V8 version (at least 4.5).

In the V8 3.19 there are API calls V8::IgnoreOutOfMemoryException() and Context::HasOutOfMemoryException() which let me don't invalidate entire isolate when some context fails with OOM and then detect that context have caused OOM. But as I can see, in the latest V8 these API calls are removed. 

So my question is: what is the current technique with latest V8 to get the same effect: don't invalidate entire isolate when some context fails with OOM and then detect that context have caused OOM?

[Ben Noordhuis]

I remember the discussion about removing those functions. The
explanation was that V8 cannot operate reliably under OOM conditions
and therefore will no longer try. In other words, there's nothing you
can do but exit.