I've used Valgrind on C programs, which worked well on those. I think you just 
ran the app like valgrind --some-args appname after compiling it with debugging 
symbols, and it tells you if there are any memory leaks and what functions they 
originate in, so it's pretty simple to use. Never tried it with Nim! I think 
it's possible from what I have read. There's a stack ulimit set on most Linux 
distros, but that would probably give a stack overflow error not an out of 
memory error.

Reply via email to