On 09/08/2014, at 10:04 AM, Ryan Gonzalez wrote: > I recently wrote a leak detector that works by defining malloc to equal > NL_MALLOC(-Dmalloc=NL_MALLOC) and putting a call to noleak_init in the main > function. If you want, I'll send you a copy for private use while you are > testing for leaks. It only shows memory that hasn't been deleted when the > program exits, so you won't see the false alarms valgrind shows.
The problem is the webserver never exits. There is no way to stop it other than a KILL. I will have to put in a way to send a GET /stop request to stop it, so that the GC can clean up before Valgrind's final report. The GC cleans up almost all memory, even the roots. Only objects like the GC itself and the world control object aren't managed by the GC. -- john skaller skal...@users.sourceforge.net http://felix-lang.org ------------------------------------------------------------------------------ _______________________________________________ Felix-language mailing list Felix-language@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/felix-language
