4 ms·
Hi @w0utert I work in the VS Code team - the experience you are having is not the experience we aspire to. It would be great to dig into this a little more an
by seanmcb 9y ago
Hi @w0utert
I work in the VS Code team - the experience you are having is not the experience we aspire to. It would be great to dig into this a little more and see what we can learn.
Perhaps the easiest way to have a deeper dialogue is via a GitHub issue. The easiest path to creating one is leveraging 'help->report issue' that will include some additional context that will help us dig in a little more.
- w0utert 9y agoThanks, I’ve definitely not given up on VS code considering how soon after I started using it I already liked it as much as I do. So if I somehow manage to isolate/reproduce some of the problems I’m seeing, I will file an issue fo it.
- lobster_johnson 9y agoAs I point out in a sibling comment, reporting aberrant behaviour can be difficult because the cause is usually unclear. Why is Code Helper using 100% CPU? Who knows. It happens every few days and doesn't seem be related to anything specific I do. More tools (such as a "task manager" similar to Chrome's) to gain visibility into what VSCode is doing would help here.
- Tyriar 9y agoFor excessive Code Helper CPU usage, you should be able to surface what the file/arguments were used to launch a Code Helper instance (how you do this depends on the OS). That will tell exactly which component is acting up, eg. TypeScript, search, terminal, extension, etc.
- lobster_johnson 9y agoThis may be a recent change? The last time I tried reporting excessive CPU usage, the Code Helper process didn't have any context info in the command line.
- Tyriar 9y agoYou find this through task manager on Windows, `ps aux | less` will work on macOS/Linux.