You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Under normal iterative development conditions BUT debug (particularly debug)
Launching NX admin-api nestjs app as follows nx run admin-api:serve:development
Developer then uses any IDE (vscode or JetBRAINS WebStorm) to launch a debug session
IDE terminates sessions fine
Whats left behind are Nx task processes
they pile up
the machine is eventually floored, cannot even render a web page
takes 30secs to even do a copy/paste operation
This is catastrophic to my current development momentum
Nx is leaving behind it a plethora of NX processes
The development machine MacBook is floored, CPU hijacked and Memory consumed
developer is left with manually (via terminal) terminating and killing each individual task left hanging running in the background
nx reset is not a solution because during intensive debugging and iteration start/stop/reload processes pile up
and we cannot see whats piling up
until the machine is unusable
then manual intervention is needed
thank you for an elite awesome product (just need finishing touches)
Expected Behavior
No processes should be left dangling consuming CPU/Memory
before after or in between
GitHub Repo
use any medium sized scaffold that develops a nestjs backend app
developer remains unimpressed with the quality of both vscode and webstorm ad neither interfaces permit turn-key debugging and setting breakpoints for backend nestjs server apps
those features are left half implemented and for the developer to hack their way thru with the variety of launch interfaces (attach/launch) much of which cannot articulate tsconfig-paths for typescript sources and sourcemaps
The text was updated successfully, but these errors were encountered:
if I launch a backend server
and it reloads with new changes to relaunch
processes start piling up in the background
it eventually gets confused after overwhelmed, starts klacking and eventually hangs
machine brought to literal halt
solution... kill terminal and cleanup anything left dangling hung
now this could be debug sessions created by webstorm since its debugger is not what it use to be
and in order to debug one has to deviate they de-coupled the entire model now
if Nx chooses to investigate this its encouraged to try and use webstorm
and debug a nestjs server app
and do the live reload over and over
and you will see the pile up of processes
Current Behavior
SUBJECT: NX task runner huge memory leak dangling processes
Under normal iterative development conditions BUT debug (particularly debug)
Launching NX admin-api nestjs app as follows
nx run admin-api:serve:development
Developer then uses any IDE (vscode or JetBRAINS WebStorm) to launch a debug session
IDE terminates sessions fine
Whats left behind are Nx task processes
they pile up
the machine is eventually floored, cannot even render a web page
takes 30secs to even do a copy/paste operation
This is catastrophic to my current development momentum
Nx is leaving behind it a plethora of NX processes
The development machine MacBook is floored, CPU hijacked and Memory consumed
developer is left with manually (via terminal) terminating and killing each individual task left hanging running in the background
nx reset is not a solution because during intensive debugging and iteration start/stop/reload processes pile up
and we cannot see whats piling up
until the machine is unusable
then manual intervention is needed
thank you for an elite awesome product (just need finishing touches)
Expected Behavior
No processes should be left dangling consuming CPU/Memory
before after or in between
GitHub Repo
use any medium sized scaffold that develops a nestjs backend app
Steps to Reproduce
nx run admin-api:serve:development
launch IDE and begin to debug
try and set breakpoints
Nx Report
Failure Logs
Package Manager Version
npm --version 10.5.1yarn --version 1.22.22
Operating System
Additional Information
developer remains unimpressed with the quality of both vscode and webstorm ad neither interfaces permit turn-key debugging and setting breakpoints for backend nestjs server apps
those features are left half implemented and for the developer to hack their way thru with the variety of launch interfaces (attach/launch) much of which cannot articulate tsconfig-paths for typescript sources and sourcemaps
The text was updated successfully, but these errors were encountered: