Is there a way to see what timeouts, intervals or async operations (or endless loops) are still running and are stopping my process from ending?
I have been able to figure it out so far without such a to开发者_如何学JAVAol, but such a tool would be very handy especially as the Node.JS projects here start to get bigger.
I am thinking of Java's kill -3
which prints a stack trace to stderr. You can do this for any process, any time, debug or no. I would like an equivalent for Node.JS. (I know that node is single threaded with async so it would output differently)
The module why-is-node-running is exactly the thing you need.
var log = require('why-is-node-running')
setTimeout(function () {
log() // logs out active handles that are keeping node running
}, 100)
And the output is something like:
There are 4 known handle(s) keeping the process running and 0 unknown
Known handles:
# Timer
/Users/maf/dev/node_modules/why-is-node-running/example.js:6 - setInterval(function () {}, 1000)
/Users/maf/dev/node_modules/why-is-node-running/example.js:10 - createServer()
# TCP
/Users/maf/dev/node_modules/why-is-node-running/example.js:7 - server.listen(0)
/Users/maf/dev/node_modules/why-is-node-running/example.js:10 - createServer()
# TCP
/Users/maf/dev/node_modules/why-is-node-running/example.js:7 - server.listen(0)
/Users/maf/dev/node_modules/why-is-node-running/example.js:11 - createServer()
# Timer
/Users/maf/dev/node_modules/why-is-node-running/example.js:13 - setTimeout(function () {
精彩评论