-
Notifications
You must be signed in to change notification settings - Fork 32.8k
Slow start up and file operation in WSL #245802
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
Comments
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.99.0. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding! |
In the latest version 1.99 we unfortunately no longer support Ubuntu 18.04 distros. If you see the same problem with other distros, I suspect the slowness is related to extensions. Can try running without extensions? |
Actually, I have disabled the extensions and test on ubuntu 22.04, it has the same problem, what logs should I check to identify the problem? ubuntu22.04.mp4 |
Can you try with VS Code 1.99.2 ? |
This issue still occurs in VS Code 1.99.2 |
@aeschli Do you have any other ways to solve this problem? It really troubles me |
Sorry, I don't. I can't reproduce on my system, and there also hasn't been any real changes to the WSL extension of VS Code remote. Is it maybe caused by mirrored mode? #198429 has a suggestion |
Yes, I set #10855 is similar to my situation, but I did not reproduce its results |
This is cause of my problem as well, thanks!! |
Does this issue occur when all extensions are disabled?: Yes/No
Description
When opening VSCode connected to WSL, the Explorer view takes an extremely long time (approximately one minute) to fully initialize. File search operations are also significantly delayed.
problem.mp4
Steps to Reproduce:
The startup performance log as follows, full content has been attached in startup performance.md, is there any other information should I provide?
startup performance.md
The text was updated successfully, but these errors were encountered: