Hm, it seems I've found something Context handle got out of visibility and thus is eligible for GC, but GC is not triggering as it seems to be enough memory(from V8 point of view)
Calling isolate->RequestGarbageCollectionForTesting(Isolate::kFullGarbageCollection); triggers context garbage collection On Sat, Jan 9, 2016 at 5:58 PM, Ben Noordhuis <[email protected]> wrote: > On Sat, Jan 9, 2016 at 3:51 PM, Sergey F. <[email protected]> wrote: > > I call this inside a c++ function, so it definitely goes out of the scope > > with the whole handle_scope... > > but memory isn't being freed > > Are you retaining a reference to the script or the result or anything > else from the context? Contexts are all-or-nothing affairs; if you > retain a reference to something inside a context, you retain it whole > (with primitives like strings and booleans being the exception.) > > You can try calling v8::Isolate::ContextDisposedNotification() when > you are sure the context is well and truly dead. I have had mixed > results with that myself so don't expect miracles. > > -- > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > --- > You received this message because you are subscribed to a topic in the > Google Groups "v8-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/v8-users/z3bVyJRyCf4/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- 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.
