-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VSCode extension is high on CPU usage #2202
Comments
Hello! |
Just to add to this report, I'm also seeing the same issue when left open for a while. I'm also having it crash the Typescript language server outright a lot. I had to disable the extension entirely. |
could you add your nx report and some details about your workspace? size for example. |
This is a large repo of about 65 projects |
I noticed the same issue as @jasonmacdonald explained on my side.
|
I have the same issue. Macbook M1 |
Having the same issue on a M1 Pro. Plus I notice that when stopping a task the node process in the activity monitor is still left running. Refreshing the workspace does clear them up again. |
I'm having issues with TS lang server either, always have to disable the extension when finished using it.
NX Report:
About VS Code:
|
please double check that you're on the latest nx console version, we've just released some fixes for the ts language server. |
Me too. I had to uninstall the extension lately as it slows down the editor. |
@demirtasdurmus can you provide some logs from the |
Current Behavior
The VSCode extension for NX Console is utilising >100% CPU, constantly. When investigating what are behind these heavy pids, it is:
/extensions/nrwl.angular-console-18.24.1/nxls/main.js
/extensions/nrwl.angular-console-18.21.4/nxls/main.js
It also seems that these processes continue to run regardless of killing VSCode or disabling the NX extension.
As a result, this significantly drains battery life when using vsc with the NX console extension.
Expected Behavior
Less CPU usage.
Steps to Reproduce
Failure Logs / Images / Videos
CPU usage in
Activity Monitor
After killing those processes:
Environment
The text was updated successfully, but these errors were encountered: