New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
High CPU usage in Remote Desktop process with WSL2 + Ubuntu #9679
Comments
Likly not an issue in the explorer, but that's where I would start to profile. The deep tree can cause a lot of file change events. Try excluding some files with the |
Yeah, I don't think it's anything within VSCode itself since I don't see high CPU usage in any node processes within WSL. I can also confirm it's not related to open file handles (I have had this before but solved it). What I have is on the order of hundreds, not tens-of-thousands:
The first of these processes watching 552 files appears to be the extension host process, which is what I'd expect with a project running TypeScript intellisense & ESLint:
|
How is Remote Desktop involved here? What I understood: You use Remove Desktop to connect to a Windows Machine that has WSL installed. On that Windows machine you run VS Code (under Window) with the WSL extension to work in WSL. |
No. I don't (consciously) use Remote Desktop at all. It seems as though its process interferes with a default WSL2 configuration somehow. All the processes in question are those I'm observing on my own local machine. |
Sorry to chime in here. I have a very similar issue on my machine. I have Docker configured to use WSL. A while after starting docker the "Remote Desktop" starts and consumes ~10% cpu. When I terminate the "Remote Desktop" in the task manager, it starts up again. Only when I shutdown wsl (and thereby kill Docker) I can then terminate "Remote Desktop" and it doesn't start again. Sometimes I have several instances of Remote Desktop running. Although I think this is related to me using remote connections in VS Code. I think the same happens when I use dev containers. In these two cases it somehow makes sense that the "Remote Desktop" process shows up. But for Docker + WSL alone, I find it weird. |
I am getting high CPU usage and an unresponsive 'explorer' sidebar in VSCode in a project with somewhat deeply nested directories (React, not Java ;). The 'loading' animation at the top of the sidebar frequently displays, and some files & directories fail to open at all.
Possibly relevant detail: my workstation is managed by a domain administrator and has Windows Defender Smartscreen enabled and locked.
At the times in which the explorer hangs (mostly when renaming, copying or creating files through the explorer) I also see high CPU usage for the Remote Desktop process on my machine but no significant activity from any Nodejs process within WSL:
The text was updated successfully, but these errors were encountered: