After I solved the problems with applications not finishing correctly I kept the the code for convenience if the problem arises again. I improved with a command line switch to do the analysis or not. I am using it as a dependency.
Recently I ran into memory problems and thanks to v8 memory dump and chrome I found the problem was whyisnoderunning. I had forgotten all about this code :-). After commenting out every reference I got rid of the memory problem.
If analzing could be stopped with an api call I could keep the dependency and keep my code.
And you should warn in the documentation and a printout when using whyisnoderunning that it is a memory hog and you risk running out of memory.
Thanks for a fantastic tool.
After I solved the problems with applications not finishing correctly I kept the the code for convenience if the problem arises again. I improved with a command line switch to do the analysis or not. I am using it as a dependency.
Recently I ran into memory problems and thanks to v8 memory dump and chrome I found the problem was whyisnoderunning. I had forgotten all about this code :-). After commenting out every reference I got rid of the memory problem.
If analzing could be stopped with an api call I could keep the dependency and keep my code.
And you should warn in the documentation and a printout when using whyisnoderunning that it is a memory hog and you risk running out of memory.
Thanks for a fantastic tool.