{"action":"created","issue":{"url":"https://api.github.com/repos/nodejs/node-v0.x-archive/issues/1025","repository_url":"https://api.github.com/repos/nodejs/node-v0.x-archive","labels_url":"https://api.github.com/repos/nodejs/node-v0.x-archive/issues/1025/labels{/name}","comments_url":"https://api.github.com/repos/nodejs/node-v0.x-archive/issues/1025/comments","events_url":"https://api.github.com/repos/nodejs/node-v0.x-archive/issues/1025/events","html_url":"https://github.com/nodejs/node-v0.x-archive/issues/1025","id":863071,"number":1025,"title":"Feature Request: Tool to see why process is still running?","user":{"login":"GeorgeBailey","id":708850,"avatar_url":"https://avatars.githubusercontent.com/u/708850?v=3","gravatar_id":"","url":"https://api.github.com/users/GeorgeBailey","html_url":"https://github.com/GeorgeBailey","followers_url":"https://api.github.com/users/GeorgeBailey/followers","following_url":"https://api.github.com/users/GeorgeBailey/following{/other_user}","gists_url":"https://api.github.com/users/GeorgeBailey/gists{/gist_id}","starred_url":"https://api.github.com/users/GeorgeBailey/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/GeorgeBailey/subscriptions","organizations_url":"https://api.github.com/users/GeorgeBailey/orgs","repos_url":"https://api.github.com/users/GeorgeBailey/repos","events_url":"https://api.github.com/users/GeorgeBailey/events{/privacy}","received_events_url":"https://api.github.com/users/GeorgeBailey/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/nodejs/node-v0.x-archive/labels/feature-request","name":"feature-request","color":"0b02e1"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2011-05-07T19:03:15Z","updated_at":"2016-05-15T20:37:51Z","closed_at":"2012-11-24T00:31:51Z","body":"Explained here http://stackoverflow.com/questions/5916066/node-js-tool-to-see-why-process-is-still-running\r\n\r\n>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?\r\n\r\n>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.\r\n\r\n>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)"},"comment":{"url":"https://api.github.com/repos/nodejs/node-v0.x-archive/issues/comments/219309105","html_url":"https://github.com/nodejs/node-v0.x-archive/issues/1025#issuecomment-219309105","issue_url":"https://api.github.com/repos/nodejs/node-v0.x-archive/issues/1025","id":219309105,"user":{"login":"fresheneesz","id":149531,"avatar_url":"https://avatars.githubusercontent.com/u/149531?v=3","gravatar_id":"","url":"https://api.github.com/users/fresheneesz","html_url":"https://github.com/fresheneesz","followers_url":"https://api.github.com/users/fresheneesz/followers","following_url":"https://api.github.com/users/fresheneesz/following{/other_user}","gists_url":"https://api.github.com/users/fresheneesz/gists{/gist_id}","starred_url":"https://api.github.com/users/fresheneesz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fresheneesz/subscriptions","organizations_url":"https://api.github.com/users/fresheneesz/orgs","repos_url":"https://api.github.com/users/fresheneesz/repos","events_url":"https://api.github.com/users/fresheneesz/events{/privacy}","received_events_url":"https://api.github.com/users/fresheneesz/received_events","type":"User","site_admin":false},"created_at":"2016-05-15T20:37:51Z","updated_at":"2016-05-15T20:37:51Z","body":"This module is super helpful for figuring out what's keeping node alive: https://github.com/mafintosh/why-is-node-running"}}