You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am consistently seeing "Initializing JS/TS language features" after working in VSCode for a while. It will slowly initialize after launch, then, within a few hours, goes back into the "Initializing" state and won't come back without a restart of VSCode.
VS Code version: Code - Insiders 1.32.0-insider (507312a, 2019-03-06T10:06:48.833Z)
OS version: Windows_NT x64 10.0.18348
System Info
Item
Value
CPUs
Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (8 x 3600)
Thanks vscodebot, but the issue is not already covered by either of those two. The feature does correctly load at first, the problem is that it stops working after some time.
mjbvz
removed
the
terminal
General terminal issues that don't fall under another label
label
Mar 7, 2019
I have this problem too. I only have 4 extensions and just 1 in common with the OP. That's the wonderful Bookmarks extension. Ah. Now if I disable Bookmarks and reload the problem seems to go away. @drayfar - Can you do the same please and confirm if this resolves the issue? If so we need to contact the author of Bookmarks.
Issue Type: Bug
I am consistently seeing "Initializing JS/TS language features" after working in VSCode for a while. It will slowly initialize after launch, then, within a few hours, goes back into the "Initializing" state and won't come back without a restart of VSCode.
VS Code version: Code - Insiders 1.32.0-insider (507312a, 2019-03-06T10:06:48.833Z)
OS version: Windows_NT x64 10.0.18348
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
Extensions (6)
The text was updated successfully, but these errors were encountered: