-
Notifications
You must be signed in to change notification settings - Fork 34.7k
Closed
Labels
terminalGeneral terminal issues that don't fall under another labelGeneral terminal issues that don't fall under another label
Description
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
Item | Value |
---|---|
CPUs | Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (8 x 4200) |
GPU Status | 2d_canvas: enabled 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 |
Load (avg) | undefined |
Memory (System) | 15.96GB (1.63GB free) |
Process Argv | |
Screen Reader | no |
VM | 0% |
Metadata
Metadata
Assignees
Labels
terminalGeneral terminal issues that don't fall under another labelGeneral terminal issues that don't fall under another label