On 14/04/2014, at 1:09 PM, john skaller wrote:
> The GC successfully deallocated 180K objects.
> Diagnostic doesn't say how many bytes but based on average 50K bytes/1K
> objects
> or 50 bytes each, 200K x 50 = 1Meg. Which is the default threshhold for the
> GC.
> So all this is looking right.
On 14/04/2014, at 11:42 AM, john skaller wrote:
> Something like this must be going on. The loop driving the tests
> and build leads to increasing number of objects. Numbers like
> 80,000 object don't make any sense. I'd have said around 1000
> max.
But this looks good:
actually collected 183302
I have a bit of a theory now on this. Its not a GC bug.
Rather, what we have is a generator or recursion making
a long chain of frames which aren't being collected
because they are, actually reachable. I suspect the
iterator generator is the culprit.
The compiler used to (and I think still does) u
