Vscode: Javascript or TS initializing

[wasimakram-mulla]

Issue Type: Bug

It keeps waiting with an error "Javascript or TS initializing..." and because of it none of my extensions work

VS Code version: Code 1.29.1 (bc24f98b5f70467bc689abf41cc5550ca637088e, 2018-11-15T19:11:49.509Z)
OS version: Windows_NT ia32 6.1.7601

System Info

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i3 CPU M 380 @ 2.53GHz (4 x 2527)|
|GPU Status|2d_canvas: enabled
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: unavailable_software
video_decode: unavailable_software
video_encode: enabled
webgl: enabled
webgl2: unavailable_off|
|Memory (System)|3.36GB (0.88GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|

Extensions (3)

Extension|Author (truncated)|Version
---|---|---
prettier-vscode|esb|1.7.2
Angular-BeastCode|Mik|7.0.18
material-icon-theme|PKi|3.6.1

[vscodebot[bot]]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• Show loading indicator while js/ts language features are first being initialized (#61636)
  

[scrossan-crown]

I am also having this issue since I upgraded to version 1.29.1. I have been having the issue with typescript / javascript language features as well as php. I use a php intellisense plugin called intelephense and it's been getting stuck loading / initializing and then doesn't provide the usual intellisense features.

[mjbvz]

Does this reproduce in the latest VS Code insiders build with all extensions disabled?

[wasimakram-mulla]

Yes, I installed VS CODE again and reinstalled all plugins

On Thu, Dec 6, 2018 at 1:09 AM Matt Bierner [e-mail]
wrote:

Does this reproduce in the latest VS Code insiders build
https://code.visualstudio.com/insiders/ with all extensions disabled?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/64412#issuecomment-444616763,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF1jAH9eR37Ocg42_4M5OWbcK3OILK4iks5u2CENgaJpZM4ZCNpI
.

--
Regards,
Wasimakram Mulla.
(9049989211)

[mjbvz]

@wasimakram-mulla Were you using VS Code insiders?

[wasimakram-mulla]

No I haven't used insiders.

I downloaded the link from the following link:
https://code.visualstudio.com/docs/?dv=win32user

On Fri, Dec 7, 2018 at 3:57 AM Matt Bierner [e-mail]
wrote:

@wasimakram-mulla https://github.com/wasimakram-mulla Were you using VS
Code insiders?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/64412#issuecomment-445052435,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF1jAJNVe6z_TrK7oUPa0fyciKdO3dZZks5u2Zm3gaJpZM4ZCNpI
.

--
Regards,
Wasimakram Mulla.
(9049989211)

[mjbvz]

Please test using the insiders build with all extensions disabled

[howzito]

I have the problem on 1.30.0 it stays there forever. As you suggested, I downloaded insiders 1.31.0 and the problem was solved.

[mjbvz]

Closing this as we need more information from original poster

[eluchsinger]

This is obviously a common problem. Why are you closing all issues related to this problem? I have the same issue.