The only safe thing for any application to do on OOM is to crash, so that's what V8 does. This is by design. There's no way around it.
On Fri, Mar 6, 2015 at 8:30 AM, madana gopal <madanagopal...@gmail.com> wrote: > > Hi, > > Also, when we throw the exception as below by creating new exception > object in FatalProcessOutOfMemory() ,Invoke() is not returned back out of > V8 execution. > > Please clarify what API can be called for the same, so that we come out of > V8.Execute(). > > Regards, > Madan > > -- > -- > 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. > -- -- 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.
