Messed isolates/isotopes up again... I mean isolates of course... On Thursday, 23 January 2014 22:55:24 UTC, Niklas Voss wrote: > > Thanks, > I was able to resolve all issues. > > Unfortunately I ran into the next issue. I am trying to implement > communication between isolates: > First I get a persistent handle of the message and then forward it to the > target isolate triggering a call- > back with the a new local handle to the message. > > Both isolates are running on different threads and I get EXC_BAD_ACCESS > when I try to instance > the persistent value (via Local<Value>::New(...)). > > Are persistent values bound to isotopes? And if, how can I pass an > arbitrary value handle to another isotope/thread? > > > On Monday, 20 January 2014 14:09:41 UTC, Sven Panne wrote: >> >> On Mon, Jan 20, 2014 at 2:55 PM, Niklas Voss <[email protected]> wrote: >> >>> [...] If the program is executed I get the following error: >>> # >>> # Fatal error in CALL_AND_RETRY >>> # Allocation failed - process out of memory >>> # >>> >>> The problem is most likely related to me using Script::New wrong or >>> context, scope issues? [...] >>> >> >> As the message says, you run out of memory at some point. It could be the >> case that e.g. you are creating too many Isolates, have some memory leaks, >> etc., it's hard to say without a tiny and complete example demonstrating >> your problem. >> >
-- -- 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/groups/opt_out.
