-
Notifications
You must be signed in to change notification settings - Fork 29k
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
Initializing js/ts language features extremely slow on WSL2 #87921
Comments
Last lines of tsserver.log on wsl2:
Similar relevant lines from tsserver.log while in Windows mode:
|
Interesting, I've left it open for a bit and it wasn't actually hung, it just took a very long time:
Over 5 minutes on wsl2. Instant on Windows. |
As a troubleshooting step, I tried the latest nightly of typescript based on this PR: microsoft/TypeScript#35615 (comment)
But it didn't help, same behavior. Edit: Also found: microsoft/TypeScript#33335 |
The issue seems to be: microsoft/WSL#4197 For now it seems that cloning the repository on the ext4 file system of wsl is the way to go. Everything is much faster, and on par with Windows performance after moving the repo and opening from ext4. Log for reference:
|
Issue Type: Bug
I have a specific workspace created using
yarn workspaces
that when opened in WSL2 will never complete the "Initializing ts/js language features" step.The problem seems to be the same as the one reported in this comment here, in an issue that was previously closed: #79380 (comment)
The last line in tsserver.log is related to an AddWatch to the main node_modules of the workspace on WSL2. No other errors otherwise.
The same tsserver.log when using Windows quickly passes that step.
The node_modules in the root of the workspace is 815MB and has 77593 files.
VS Code version: Code 1.41.1 (26076a4, 2019-12-18T14:58:56.166Z)
OS version: Windows_NT x64 10.0.19041
System Info
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off
surface_control: disabled_off
surface_synchronization: enabled_on
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: