Re: Tracing Memory Grabbers

[Dimitris Papavasiliou <dpapavas@...>]

So while we're on the subject, and since we can always ask the gc how
much memory is allocated at a given instance but not where this memory
is used.  Is there a way of finding out what values are still alive in
the Lua state, and if possible, why they're still alive?  It's a
problem I've been having on and off.  Sometimes I see that a whole
tree of values I expected to get rid off still linger but it's not
always trivial, tracing why they aren't collected.

On Fri, Mar 16, 2012 at 6:29 PM, Luiz Henrique de Figueiredo
<lhf@tecgraf.puc-rio.br> wrote:
>> keeping count inside the allocator and asking
>> the collector give the same result?
>
> Yes.
>