This is (very) hard to pull off, because there are references between the spaces that all need to be considered to determine the full transitive hull of all reachable objects. So no matter which of the "old spaces" (like code space) you want to collect, the entire managed heap needs to be considered.
One exception is the "new space" (i.e. the young generation), this one can be collected independently, because V8 has all the machinery (i.e. write barriers, remembered set, and so forth) in place to keep track of inter-generational references. To sum it up: GC on just the code space is not supported. :) Best regards, Michael On Mon, Dec 22, 2014 at 1:25 AM, Chris <[email protected]> wrote: > Hi > > I try to make v8 GC on a specific space, code space. > > Could you give me an approach or a hint to make it or help me > > if you have some experience or a solution of this problem? > > Thanks. > Chris. > > -- > -- > v8-dev mailing list > [email protected] > http://groups.google.com/group/v8-dev > --- > You received this message because you are subscribed to the Google Groups > "v8-dev" 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. > -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" 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.
