Open superhawk610 opened 6 years ago
I have also had exactly this - using VS Code 1.28.2, Flow for Visual Studio Code 0.8.4 on Windows 7 Pro.
Had to restart my machine...
@stephen-last I almost posted this as a comment on your issue, but I'm not sure if they share the same cause. Those logs are from Ubuntu 18.04, but I've also experienced the same lag on Windows 10 Pro.
experienced the same on Mac
I'm not too familiar with the code but it looks like it just blindly spawns and/or exits, but on exit does not end the process. May try put in PR this weekend as I've done some Node process management in the past.
Brief summary of something I think could help (at the very least make the code more robust):
Edit: whoops. This is for the flow-bin
repo, which I was subsequently looking into. It shouldn't be spawning this many processes to begin with though, so that wouldn't solve this either (just possibly help make it manageable resource wise on PCs).
Below I've attached the output of
ps -ef | grep flow
after an hour or so of developing in VS code using this extension. As you can see, hundreds offlow-bin
processes are spawned and seemingly left running, which eventually bogs my computer down and makes it unusable.Has anyone else experienced this behavior or have any ideas as to how to remedy it?