Take the 2-minute tour ×

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 tool, 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)

share|improve this question
I had a similar problem, are you running into this issue when running tests with some sort of database? For example, my unit tests when I was using mongodb would never exit because of the internal mongo timeouts/intervals. –  kcbanner May 6 '11 at 19:44
@kcbanner: In MySQL, you have to end the connection before the process will do an auto exit. It may be the same in mongodb? Or did you already try that? –  George Bailey May 6 '11 at 20:48
Yea, ending the connection fixes it. –  kcbanner May 7 '11 at 18:00
add comment

1 Answer

up vote 6 down vote accepted

Posted a feature request https://github.com/joyent/node/issues/1025

share|improve this answer
That would be great. –  Amjad Masad May 8 '11 at 9:35
add comment

Your Answer


