Re: Tracing Memory Grabbers

[Axel Kittenberger <axkibe@...>]

Thank you all, found it! It was indeed in the Lua part and not in C core:

I said:
    setmetatable(e2s, { __mode = 'k' })
where it should have been
    setmetatable(e2s, { __mode = 'kv' })

And
    setmetatable(e2d, { __mode = 'k' })
where it should have been
    setmetatable(e2d, { __mode = 'v' })

;-)

Oh the weak tables! I curse on Javascript all the time, for not having
them at all and thus not giving me any chance to intern immutable
constructs like 2D-Pointers, but on the other hand, they also can be
tricky to get right.

kind regards,
Axel

On Fri, Mar 16, 2012 at 3:37 PM, Jorge <xxopxe@gmail.com> wrote:
> On vie, 2012-03-16 at 09:48 +0100, Axel Kittenberger wrote:
>> But how to approach Lua, is there some list
>> of all allocated objects somewhere? Or some info How much memory the
>> Lua VM needs?
>
> Dumps state:
> http://lua-users.org/lists/lua-l/2006-07/msg00110.html
>
> What about a huge dot graph:
> http://lua-users.org/lists/lua-l/2009-11/msg00491.html
>
>
>
> Jorge
>
>
>