While working on a full-stack application it might happen that you end up with a bunch of node processes running at the same time.
It could be som...
For further actions, you may consider blocking this person and/or reporting abuse
It's usually good to try a
kill -15 PROCESS_IDbefore resorting tokill -9, since it gives the stuck process a chance to clean up before dying.Probably overkill for local development servers, but definitely preferrable for things that may have state such as a database.
thanx for pointing this out. :-)
Thank you a lot
How did you format your output? Mine appears as a wall o' text like this:
502 1128 1125 0 3:17PM ?? 0:31.12 /Applications/Reactotron.app/Contents/Frameworks/Reactotron Helper (Renderer).app/Contents/MacOS/Reactotron Helper (Renderer) --type=renderer --field-trial-handle=1718379636,9355752010542677649,1429803248351936294,131072 --disable-features=SpareRendererForSitePerProcess --lang=en-US --app-path=/Applications/Reactotron.app/Contents/Resources/app.asar --node-integration --no-sandbox --no-zygote --background-color=#fff --num-raster-threads=2 --enable-zero-copy --enable-gpu-memory-buffer-compositor-resources --enable-main-frame-before-activation --service-request-channel-token=3685712697854128908 --renderer-client-id=5 --no-v8-untrusted-code-mitigations
502 15785 15718 0 6:18PM ?? 0:15.06 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Renderer).app/Contents/MacOS/Code Helper (Renderer) --type=renderer --disable-color-correct-rendering --field-trial-handle=1718379636,9347403567474433047,3772520779013372132,131072 --disable-features=LayoutNG,PictureInPicture,SpareRendererForSitePerProcess --lang=en-US --standard-schemes --secure-schemes=vscode-resource --bypasscsp-schemes --cors-schemes=vscode-resource --fetch-schemes=vscode-resource --service-worker-schemes --app-path=/Applications/Visual Studio Code.app/Contents/Resources/app --node-integration --no-sandbox --no-zygote --background-color=#282a36 --disable-blink-features=Auxclick --num-raster-threads=2 --enable-zero-copy --enable-gpu-memory-buffer-compositor-resources --enable-main-frame-before-activation --service-request-channel-token=1663595825542118109 --renderer-client-id=7 --no-v8-untrusted-code-mitigations
502 18962 15718 0 11:15AM ??
what about killall node
That's all. Still this is a nasty issue. On ubuntu after several debug sessions, the memory runs out and as known, linux cannot deal with that.
Just run killall before debug, also is not a real solution.
Thanks for this !
Thanks a lot I'm not longer stocked now
Thank you so much. This article really helped me solve a problem that was messing with me.
Thank you! Helped a lot!!!
Hello I'm unable to kill this DO I have to kill usr/local/bin/node index.js. I tried by its process ID but nothing shows
lovin' this::: lsof -i :3001
thanks