Re:Integrated Terminal Performance Improvements
by lobster_johnson on Wednesday October 04, 2017 @05:12PM
(#15404726)
As 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.
[ Parent
| on HN ]
Re:Integrated Terminal Performance Improvements
by Tyriar on Wednesday October 04, 2017 @05:35PM
(#15404916)
For 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.
Re:Integrated Terminal Performance Improvements
by lobster_johnson on Wednesday October 04, 2017 @06:20PM
(#15405235)
This 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.