Thanks everyone for the answers.
Yes, we call it memory hoarding. It is not a definitive name yet, but we are working on that.
I will take a look at the options for tracking the problem.
But what I am actually looking for are running programs with the symptoms (huge increasingly memory use), so I can analyze them and improve my research. If anyone has a program with excessive memory consumption synmptons and is whilling to share, that would be perfect.
Thanks again,
Pablo Musa
Em Domingo, 4 de Maio de 2014 12:29, Ignacio Burgueño <iburgueno@gmail.com> escreveu:
On Sat, May 3, 2014 at 7:19 AM, Philipp Janda
<siffiejoe@gmx.net> wrote:
Your wish is my command: I've added an option to microscope which uses lua-getsize if available in CPATH on userdatas, tables, functions, and threads (Lua 5.1 only obviously). An example can be seen here[1]. However, I have no idea how an integration with luatraverse would look like (I do my own traversal), and I have some unresolved issues with lua-getsize:
Having written many long running services with luanode, and spent hours debugging memory consumption issues, having this tool available is great. Many thanks.
