Thanks Ben for your reply. I am able to avoid the problem by making sure I'm in an Isolate while disposing another one. This basically means that I'll always have at least one Isolate around, which is probably the assumption of the design.
Jane On Wednesday, March 12, 2014 1:23:14 PM UTC-7, Ben Noordhuis wrote: > > On Wed, Mar 12, 2014 at 8:15 PM, Jane Chen <[email protected]<javascript:>> > wrote: > > I am creating an Isolate when needed, and trying to dispose it when > done. I > > wonder whether the assumption is that I have to be in an Isolate in > order to > > dispose an Isolate, since I'm getting: > > > > # > > # Fatal error in ../src/isolate.h, line 452 > > # CHECK(isolate != __null) failed > > # > > > > ==== C stack trace =============================== > > > > 1: V8_Fatal > > 2: v8::internal::Isolate::Current() > > 3: v8::Utils::ReportApiFailure(char const*, char const*) > > 4: v8::Utils::ApiCheck(bool, char const*, char const*) > > 5: v8::Isolate::Dispose() > > > > Please advise. > > > > Thanks! > > It's difficult to say what exactly is going on without accompanying > code but it sounds like the isolate is still active / entered when you > call Isolate::Dispose(). Maybe you forgot to call Isolate::Exit() or > perhaps an Isolate::Scope object is not scoped properly? > -- -- v8-users mailing list [email protected] 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
