On Thu, Sep 02, 2010 at 11:20:52AM -0400, Will Coleda wrote: > > Currently each eval() execution results in compiling and > > loading at least two additional Parrot subs into memory > > that represent the eval'ed code. As far as I can tell, > > once loaded there's currently no way for a Parrot Sub PMC > > to become "unloaded" or GC'ed -- it stays in memory until > > the process ends. So, it's not too surprising the above leaks. > > > > We probably need to file a Parrot ticket to get Parrot to > > support garbage collection of Sub PMCs when they're no > > longer used. > > I wonder if this related to http://trac.parrot.org/parrot/ticket/783
Indeed it is, the script in that ticket is quite similar to the one I used to verify that anonymous subs don't get gc'd. Great catch, we can keep an eye on TT #783 for this one. Pm
