Run away node processes

[ccaspanello]

Current Behavior

Run away processes before getting frustrated and killing all processes

% ps -ax | grep node | wc -l
     717

After running killall node

% ps -ax | grep node | wc -l
       1

Waiting a few seconds

% ps -ax | grep node | wc -l
       3

These 3 are:

<APPLICATIONS_FOLDER>/WebStorm.app/Contents/plugins/javascript-plugin/jsLanguageServicesImpl/js-language-service.js
<PROJECT_FOLDER>/node_modules/.pnpm/[email protected]/node_modules/typescript/lib/typingsInstaller.js
grep node

These are expected

Starting my backend and frontend projects with Webstorm (run frontend & debug backend)

% ps -ax | grep node | wc -l
      24

Right now I am unable to get the process count to go above 25 when I start/stop the debugger or even intentionally crash the debugger by putting in bad typescript. I'll run for a few hours and monitor this and if I see the process creep up again I'll attach the process log to this ticket.

Expected Behavior

I understand certain deamons run, but the number of processes shouldn't get this high for 2 projects

Steps to Reproduce

Hard to say, I do not have an open source project to share. Curently we have the following:

• NestJS App (backend)
• Vite Web App react-ts (frontend)
• 2 backend libraries
• 2 frontend libraries

Failure Logs / Images / Videos

/Users/____/Desktop/git/idplans/idplans-platform/node_modules/.bin/nx run backend-api:serve:development
Debugger listening on ws://127.0.0.1:56832/f158e5e5-e261-4c2c-8071-499bb99e9293
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.

 NX   Running target serve for project backend-api and 2 tasks it depends on:

———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

> nx run backend-reports:build  [existing outputs match the cache, left as is]


> nx run backend-api:build:development  [existing outputs match the cache, left as is]

> webpack-cli build node-env=development

Debugger listening on ws://127.0.0.1:62989/8d76246e-063d-4faf-bb3c-2ae84c33393f
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Debugger listening on ws://127.0.0.1:63000/00122a29-6f23-4dfd-966c-b654e11988c8
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Debugger listening on ws://127.0.0.1:63002/8211c4ac-8dac-4f1f-ab88-af4735e0b495
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
chunk (runtime: main) main.js (main) 396 KiB [entry] [rendered]
webpack compiled successfully (07c3b0e2c19cfd16)
Waiting for the debugger to disconnect...

> nx run backend-api:serve:development

Debugger listening on ws://127.0.0.1:56864/c0652f60-7815-4542-95f8-5235392da992
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Debugger listening on ws://127.0.0.1:56870/357072ce-b457-4ef5-bb41-1fe9537c9de7
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Debugger listening on ws://127.0.0.1:56876/b58febbe-d752-408d-b230-ad8f22bdf2d1
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.

   ✔  1/1 dependent project tasks succeeded [1 read from cache]

   Hint: you can run the command with --verbose to see the full dependent project outputs

———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————


> nx run backend-api:build:development  [existing outputs match the cache, left as is]

> webpack-cli build node-env=development

Debugger listening on ws://127.0.0.1:62989/8d76246e-063d-4faf-bb3c-2ae84c33393f
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Debugger listening on ws://127.0.0.1:63000/00122a29-6f23-4dfd-966c-b654e11988c8
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Debugger listening on ws://127.0.0.1:63002/8211c4ac-8dac-4f1f-ab88-af4735e0b495
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
chunk (runtime: main) main.js (main) 396 KiB [entry] [rendered]
webpack compiled successfully (07c3b0e2c19cfd16)
Waiting for the debugger to disconnect...

———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 NX   Successfully ran target build for project backend-api and 1 task it depends on (159ms)

Nx read the output from the cache instead of running the command for 2 out of 2 tasks.

Debugger listening on ws://127.0.0.1:56885/e10e6fe7-f20d-417b-a80b-3ccb0439e365
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Waiting for the debugger to disconnect...
Waiting for the debugger to disconnect...
Debugger listening on ws://localhost:9229/34223793-5028-485a-a1be-23902d8857c4
Debugger listening on ws://localhost:9229/34223793-5028-485a-a1be-23902d8857c4
For help, see: https://nodejs.org/en/docs/inspector

Debugger attached.

[Nest] 43838  - 01/10/2025, 9:03:32 AM     LOG [NestFactory] Starting Nest application...

Environment

Node           : 23.5.0
OS             : darwin-arm64
Native Target  : aarch64-macos
pnpm           : 9.15.1

nx (global)        : 20.0.10
nx                 : 20.1.1
@nx/js             : 20.1.1
@nx/jest           : 20.1.1
@nx/eslint         : 20.1.1
@nx/workspace      : 20.1.1
@nx/cypress        : 20.1.1
@nx/eslint-plugin  : 20.1.1
@nx/nest           : 20.1.1
@nx/node           : 20.1.1
@nx/react          : 20.1.1
@nx/vite           : 20.1.1
@nx/web            : 20.1.1
@nx/webpack        : 20.1.1
typescript         : 5.7.2
---------------------------------------
Registered Plugins:
@nx/vite/plugin
@nx/eslint/plugin
@nx/cypress/plugin
@nx/jest/plugin
@nx/webpack/plugin

• Nx Console version:
  Nx Version:

• Local: v20.1.1

• Global: v20.0.10

• VSCode version:
  Webstorm Build #WS-243.22562.112, built on December 4, 2024

[MaxKless]

Hey @ccaspanello sorry you're running into trouble and thanks for trying to make Nx Console better.
Could you help me understand how Nx Console plays into this here? It looks to me like the issues you're facing are related to other processes that aren't being killed.

[ccaspanello]

I apologize. This may actually be a Webstorm NX Plug-in issue. Would you happen to know the bug tracking system for that? I can copy/paste the issue over there.

[MaxKless]

this is still the right place for jetbrains issues. I just need to understand what's going on better