Hey @r3volution11, thanks for reporting this and for all of the info. When you experience the issue again, can you try running the Developer: Open Process Explorer command to try to see which process within VSCode is consuming CPU? More info on that here: https://github.com/microsoft/vscode/wiki/Performance-Issues#visual-studio-code-is-consuming-a-lot-of-cpu

We also have builds targeting a much newer version of our UI framework (Electron version 6.0.x). Can you give that version a try? Download:

• macOS: Download
• Linux (DEB): Download
• Linux (RPM): Download
• Windows: Download

Activity Monitor Screenshot: http://r3v.in/LlijA/Screen-Shot-2019-08-21-11-31-23.74.png

Process Explorer Screenshot: http://r3v.in/k3YTT/Screen-Shot-2019-08-21-11-32-24.29.png

I've seen the process explorer look different before with several instances. I don't recall it ever being so bare as it is there.

I'll try using one of the newer builds. Thanks for your help!

Update: Here's a new shot of the Process Explorer as it typically looks: http://r3v.in/i7yNR/Screen-Shot-2019-08-21-11-45-41.72.png

VS Code Exploration Screenshots:

Activity Monitor: http://r3v.in/OQsR3/Screen-Shot-2019-08-21-11-40-18.88.png

Process Explorer: http://r3v.in/xAvgK/Screen-Shot-2019-08-21-11-39-10.53.png

If anything the problem "feels" worse here.

FYI, I also disable git.

Approximately 30 minutes after opening, on the regular build, the CPU usage is back to normal.

Ah, ok! The last process explorer screenshot and your observation that it stops some time after opening make me think this is related to a telemetry event we log on startup. We log data about what file types are in the current workspace so we get a sense of what languages are being used in VSCode. This is from within the "shared process" and involves walking the file tree, I think this would be expensive over SMB.

Can you try disabling telemetry by unchecking the "Telemetry: Enable Telemetry" setting and see if it still repros to confirm if this is the case?

Yes, it still happens.

Process Explorer: http://r3v.in/nYszL/Screen-Shot-2019-08-21-13-05-14.79.png
Activity Monitor: http://r3v.in/ziapn/Screen-Shot-2019-08-21-13-05-51.52.png

You got my hopes up. 😆

I guess another question is: should I use something other than SMB?

Haha, sorry! I actually still think it's this code that's a problem, the shared process is still high in the screenshot you sent and there's not much heavy lifting it does besides that.

Looking at the code that logs this event - if telemetry is disabled, it still does the whole computation and sends it to the telemetry service. The service checks if telemetry is disabled at that point and will ignore it if so. I can add an earlier check to prevent the work being done in that case, and look into improving the perf of the event computation.

If you're able to SSH into your VM instead, that would be more performant. Some info on that: https://code.visualstudio.com/docs/remote/ssh

Edit: Actually, ignore that, that wouldn't work for you currently since it's a windows VM 😢

Yea, I'd love to take advantage of the remote ssh extension. I'm actually one of the first to write up an issue about it (microsoft/vscode-remote-release#25).

What I don't understand is that this problem doesn't occur with all of my projects on this VM. There's one in particular and I can not for the life of me figure out why. 7 projects, all very close to the same but different frontends.

Can you try running code --status from the terminal when that project is open, and when a project without the problem is open, and report the output? It should include a "Workspace Stats" section about number and types of files

I think Code is upset with me. I opened a local, small project and the shared process ate up the CPU as well this time. I quit Code but the processes were left hanging and needed to be force quit. Reopened the project in Code and ran code --status and it gave me this:

Attempting to run the command with a project that has problems does not return any information. It just sits there.

Okay, I let it just sit there doing it's thing. Here it is:

I see it's reporting tons of images and dll's when I've ignored a majority of directories that contain those file types.

@r3volution11 I made a change yesterday that should improve perf somewhat, can you give it a try? https://code.visualstudio.com/insiders/

The problem remains on open, however, it does appear to dissipate more quickly.

@RMacfarlane Will whatever you did in Exploration eventually make it into the main release? I'd at least be happy to see that. I just opened up a project in the latest main release and the problem hit big time.

@r3volution11 Yes, the changes I made in the Insiders version should be available in the stable release that just shipped, version 1.39

I'm going to go ahead and close this since it's now been 2 years and we haven't had further reports of this. Sorry for the incredible delay. Please open a new issue if you're still seeing problems. Thanks!