I’d like to thank you all for your old age. The situation is as follows.
I wrote a crawler with nodejs. In the process of crawling out, the code may enter such a situation: it died there without reporting an error or continuing to execute. Because the memory usage has been very high, it is not sure whether the memory is used up or whether it is stuck in a dead loop for some other reason. Therefore, I want to know if there is any way to analyze this situation. Thank you.
Below webkit: node-inspector module provides such a possibility. Node-inspector installed via npm
Npm install -g node-inspector // -g import installation path to environment variable
Node-inspector turns to debug input and output through websocket. Therefore, we need to start node-inspector to listen to the debug debug port of Nodejs before debugging.
To do a good job, one must first sharpen one’s tools –Nodejs debugging technology summarizes many tools