improve leak detection heuristics

Open lloyd opened this issue 13 years ago • 1 comments

the current heuristic is very simple, it just looks for consecutive growth over 5 successive GCs.

We can do better, yes we can.

Jun 29 '12 10:06 lloyd

I don't know whether this is related but memwatch is not notifying me about memory leaks but i can see the memory usage go way up in htop. I'm doing this in a test environment specifically build to test the node app so there is nothing else that eats memory.

The memory increase initially is quite quick. About 50mg up for 1 min and then is not by much but it is steady.

So, could this be related?

Apr 12 '13 22:04 antitoxic