Re: Debugging memory leaks

[Kim Alvefur <zash@...>]

Hi,

On Wed, May 15, 2019 at 05:45:29PM -0400, Sean Conner wrote:
>   Okay, I realize Lua has GC, so it's not a leak per se, but I am somehow
> keeping references to data somewhere, and I can't seem to track them down. 
> The last time I encountered this issue, I was able to study the code and
> through deductive reasoning, found the issue [1].

I did some work on a memory visualization tool that would plot used
memory over a hilbert curve. The data collection part grew into this
library: <http://luarocks.org/modules/zash/lua-mtrace>

Unfortunately I've yet to write any good tooling for finding
unexpectedly long-lived allocations, other than tediously typed out awk
programs that weren't saved.

-- 
Kim "Zash" Alvefur

Attachment: signature.asc
Description: PGP signature