{"action":"created","issue":{"url":"https://api.github.com/repos/remy/nodemon/issues/1025","repository_url":"https://api.github.com/repos/remy/nodemon","labels_url":"https://api.github.com/repos/remy/nodemon/issues/1025/labels{/name}","comments_url":"https://api.github.com/repos/remy/nodemon/issues/1025/comments","events_url":"https://api.github.com/repos/remy/nodemon/issues/1025/events","html_url":"https://github.com/remy/nodemon/issues/1025","id":227753239,"node_id":"MDU6SXNzdWUyMjc3NTMyMzk=","number":1025,"title":"Nodemon frequently leaves the child process running (detached)","user":{"login":"callumlocke","id":250617,"node_id":"MDQ6VXNlcjI1MDYxNw==","avatar_url":"https://avatars2.githubusercontent.com/u/250617?v=4","gravatar_id":"","url":"https://api.github.com/users/callumlocke","html_url":"https://github.com/callumlocke","followers_url":"https://api.github.com/users/callumlocke/followers","following_url":"https://api.github.com/users/callumlocke/following{/other_user}","gists_url":"https://api.github.com/users/callumlocke/gists{/gist_id}","starred_url":"https://api.github.com/users/callumlocke/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/callumlocke/subscriptions","organizations_url":"https://api.github.com/users/callumlocke/orgs","repos_url":"https://api.github.com/users/callumlocke/repos","events_url":"https://api.github.com/users/callumlocke/events{/privacy}","received_events_url":"https://api.github.com/users/callumlocke/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":82,"created_at":"2017-05-10T17:23:15Z","updated_at":"2019-08-15T12:29:38Z","closed_at":"2017-12-13T13:43:27Z","author_association":"NONE","body":"I am using Nodemon to restart an Express server in development. I even clean up with `server.close()` on process exit. But I frequently get \"Port 3000 is already in use\" when it starts, suggesting nodemon failed to kill the old child process, and it is still running as a detached process. I have to kill nodemon, run `killall node`, and restart nodemon again. Is this a known problem? Are there any workarounds?\r\n\r\n- OS X El Capitan\r\n- Node v7.10.0.\r\n- nodemon v1.11.0"},"comment":{"url":"https://api.github.com/repos/remy/nodemon/issues/comments/521623974","html_url":"https://github.com/remy/nodemon/issues/1025#issuecomment-521623974","issue_url":"https://api.github.com/repos/remy/nodemon/issues/1025","id":521623974,"node_id":"MDEyOklzc3VlQ29tbWVudDUyMTYyMzk3NA==","user":{"login":"hondem","id":17029828,"node_id":"MDQ6VXNlcjE3MDI5ODI4","avatar_url":"https://avatars0.githubusercontent.com/u/17029828?v=4","gravatar_id":"","url":"https://api.github.com/users/hondem","html_url":"https://github.com/hondem","followers_url":"https://api.github.com/users/hondem/followers","following_url":"https://api.github.com/users/hondem/following{/other_user}","gists_url":"https://api.github.com/users/hondem/gists{/gist_id}","starred_url":"https://api.github.com/users/hondem/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hondem/subscriptions","organizations_url":"https://api.github.com/users/hondem/orgs","repos_url":"https://api.github.com/users/hondem/repos","events_url":"https://api.github.com/users/hondem/events{/privacy}","received_events_url":"https://api.github.com/users/hondem/received_events","type":"User","site_admin":false},"created_at":"2019-08-15T12:29:38Z","updated_at":"2019-08-15T12:29:38Z","author_association":"NONE","body":"I'm having the same issue right now. Tried to debug event loop if there is anything left but seems like no.\r\n\r\n```\r\n\"nodemon\": \"^1.19.1\",\r\nnode: v10.16.2\r\nnpm: 6.9.0\r\n```\r\n\r\nHas anybody figured out the right, clean solution for this? "}}
{"actor":{"display_login":"hondem"}}