Hi Pavel! Already using this thing to give v8 an estimate of external memory it indeed helps to call GC during the JS life cycle But the thing that V8 does not call weak callbacks when context is being garbage collected is still kind of mystery for me(imo it's wrong)
On Sat, Jan 9, 2016 at 6:54 PM, Pavel Medvedev <[email protected]> wrote: > Hi Sergey, > > On Saturday, January 9, 2016 at 6:14:17 PM UTC+3, Sergey F. wrote: >> >> 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 >> >> >> > You mentioned about large amount of memory allocation on C++ side. There > is a v8::Isolate::AdjustAmountOfExternalAllocatedMemory() function to > notify GC in V8 about such memory allocations. Maybe it would help. > > -- > -- > 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.
