4 ms·
Huh? I am not a big fan of VSCode (for other reasons [0]), but I have its windows on multiple monitors all the time. Works fine. Can't even understand how a pro
by jhugo 4y ago
Huh? I am not a big fan of VSCode (for other reasons [0]), but I have its windows on multiple monitors all the time. Works fine. Can't even understand how a program could stop that working.
[0] It chews enormous amounts of CPU and RAM, and periodically gets into a state where it won't open the "Open file" dialog for unknown reasons. And occasionally renaming a file brings up something like "Running 'Rename file' participants..." which hangs for 15+ minutes. Absurd.
- can16358p 4y agoInteresting. What languages/plugins/processes are you using? I'm a TypeScript/React/React Native dev and Vscode is butter smooth with very minimal CPU and RAM usage (after offsetting the Electron overhead).
- jhugo 4y agoWhy would you offset the Electron overhead? Plenty of other editors don't use web tech, so it doesn't make sense to give VSCode a free pass for choosing to use it. Anyway, I tried running with no plugins for a while, and still had the problems (open file dialog failing, and random occurrences of "running file rename participants" hanging for a long time) occasionally. It happens sporadically on both my M1 MacBook Air running macOS and my Threadripper workstation running Linux, even with no shared config and only editing local files, so I am pretty sure it's just buggy VSCode. I found numerous old bug reports about similar issues. All closed without resolution after being ignored for months. Edit: oh, and about the CPU and RAM, this is mostly an issue on my MacBook — VSCode is the only software I have ever found that will make it noticeably lag sometimes. I can always close it and open it again with the same files and it will work perfectly for another few days.