Since recently, VSCode started to eat 90% CPU per window even in idle mode. I suspect, some of plugins could be responsible for it.
Is there a way to somehow profile VSCode, so I could find the offending plugin?
I had a clean installation on another machine with minimal amount of plugins, and the problem is not there.
Check if you have settings-sync extension. Its known for high CPU utilization. Disable it, restart VSCode, kill Code helper (all) and start again. it will use again 100% for few seconds and it will drop to normal 8-10%
https://marketplace.visualstudio.com/items?itemName=Shan.code-settings-sync&ssr=false#review-details
Related
In VS Code V1.73.1 - I am running GDB (actually a RISCV variant, debugging a target board vi jtag).
I"m also quite a bit confused and do not know if this is a VSCODE problem or a plugin problem, and there are multiple plugins involved,
If it is a plugin then I'm thinking it is the one that controls GDB... and other things are built upon that plugin. But - GDB is so much at the core that I think that the GDB component is actually part of the baseline VS-CODE package.
Background: I want to halt the cpu I am debugging so that i can inspect global variables and/or set breakpoints. I cannot seem to do that.
I normally go through the connect, load, then type continue. If I set a breakpoint before I type continue - it works.
My code is now running, I want to stop - add a breakpoint and continue.
To be clear - I do not mean disconnect and stop debugging, I want to stop or halt the cpu at its current location.
The normal method or action for GDB is to type Control_C in the GDB terminal but - this is VS Code, its not a normal terminal.
The question is how do I stop or halt the cpu under control of the debugger
Its not obvious, and no menu seems to find that selection.
if it was an local debug session I could do something like controlC in a console window or use KILL to send a signal, but - this is an embedded/remote GDB session so that is not possible.
Problem
Every time I use Eclipse on my personal laptop, it constantly freezes (e.i. the process stops responding) for seemingly everything I do except for regular typing (without content assist). Any other action will cause it to freeze 7 out of 10 times, for roughly 10-20 seconds, mainly:
Any automatic proposal menus (e.g. when you type . after a variable name and a list of options appears) or manual ones (e.i. Ctrl + Space).
Any auto-import (Ctrl + Shift + O) or auto-format (Ctrl + Shift + Space)
Any context menu
Viewing JavaDoc comments
Any interaction with the project/package explorer
Any load/save operations
Any run/debug operation
Exiting the program
Every once in a while, it will not freeze, but the content assist will take a very long time to give me proposals, or the JavaDoc info will take a long time to load.
I use Eclipse on my work laptop and I do not experience any of these issues.
Things I've tried
Increase the RAM
Monitor the heap (I did not observe any correlation between heap size and freezing)
Move my workspace from my external drive to my internal drive
Run eclipse -clean
Perform a clean installation:
Delete the installation directory (%userprofile%\eclipse\java-XXXX-XX\eclipse)
Delete the .p2 directory (%userprofile%\.p2)
Download and install the latest version of Eclipse
Create a new workspace (and test it by creating a new project instead of importing old ones)
Disable the "Override high DPI scaling behavior" option (see this)
Environment
I am sure that someone is going to ask if I have a computer capable of running Eclipse. These are my laptop's specifications:
GPU : NVIDIA GeForce RTX 3070 Laptop GPU
CPU : AMD Ryzen 9 5900HS with Radeon Graphics
Memory: 16 GB RAM (15.41 GB RAM usable)
It's a ROG Zephyrus G15 (Model: GA503QR_GA503QR). I previously owned a G14 and had the same issue.
Observations
I notice that often when this happens explorer.exe also stops responding. I can still use other applications like Google Chrome, but I have to wait for Eclipse to respond before Windows Explorer starts responding.
Question
What are the potential causes of the described behaviors, and remedies thereof?
I wonder what is the electron_node bundle.js process doing exactly in VS Code, it's using a lot of CPU and makes my laptop very noisy even when just editing a single file.
It looks it's from the pylance, but I don't see it in the vscode on another laptop. I'm confused where it's exactly from. Any insight would be appreciated.
I'm using vscode 1.54.3
Update:
Looks it's a pylance issue, after I downgrade it from 2021.3.3 to 2021.2.4. it's not consuming much cpu anymore.
I'm trying to move from Netbeans IDE to VS Code. I have a fresh instalation (newest version 1.29.0) without any extensions on Windows 8.1.
When I try to search a file by CTRL+E immedietly Antimalware Service Executable process (Windows Defender) spikes CPU usage for a second and my CPU fan goes nuts. Even before I type to search anything. It's very annoying.
I have excluded code.exe from Windows Defender and the entire folder within I'm trying to search. It helped a little - 98% CPU usage lowered to like 40%. Still not the result I was hoping for.
CPU is Intel Core i7-2600.
What am I doing wrong?
I believe that this is a bug in VS code. A couple of issues have been raised about it on GitHub in the last few days:
https://github.com/Microsoft/vscode/issues/63070
Sometimes the connection to the server has problems and the automatic uploading feature just goes away. When this happens the file cannot automatically get uploaded after editing.
How can I re-enable automatic uploading? The only way I know is to restart the netbeans IDE. Is there a better, faster way?