Initializing js/ts language features never completes

[brunoscopelliti]

I've just installed version 1.37.1.
It seems there has been a regression on this issue: #68896.

[mjbvz]

/needsMoreInfo

[vscodebot]

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.

Happy Coding!

[brunoscopelliti]

Hi @mjbvz ,
What kind of info do you need?
The issue is exactly the same of #68896.

[electric-skeptic]

VS Code version: 1.37.1
Windows 7 Starter 32 bit

Extensions (problem exists with all disabled):
vscode-eslint dba 1.9.0
githistory don 0.4.6
gitlens eam 9.9.3
vscode-settings-cycler hoo 1.0.1
git-graph mhu 1.13.0
vscode-typescript-tslint-plugin ms- 1.2.2

Steps to reproduce:
open any JavaScript or TypeScript file

Symptoms:
The application starts responding very slowly and

"Initializing Js/TS language features"

appears in the statusbar, which never disappears.

As @brunoscopelliti mentioned the issue presents with the exact same symptoms as all of the other times it's been reported and closed previously (normally for insufficient information, or just locked with no explanation).

[mjbvz]

Have you configured a custom TypeScript version in your workspace? Are you loading a file on a network drive?

[electric-skeptic]

Hi @mjbvz No, the files are all on the local hard drive. There aren't any workspace settings at all, nor have I made any effort to set up TypeScript beyond installing the TSLint extension.
It's also a clean install of VS Code on a laptop not previously used for any development

[mjbvz]

Please try collecting the TS Server log:

1. Set "typescript.tsserver.log": "verbose",
2. Restart VS Code and reproduce the problem
3. In VS Code, run the TypeScript: Open TS Server log command
4. This should open a large log file called tsserver.log

If you can share the log, I can also take a look to see if anything stands out

⚠️Warning: The TypeScript log may include information from your workspace, including file paths and source code. If you have any concerns about posting this publicly on Github, just let me know and we can arrange something else. On our side, we only use these logs to investigate issues like this

[mjbvz]

Also @electric-skeptic, open a separate issue

[remychvn]

I confirm, I encounter the same issue.
I'm not using typescript. I have only two vscode extensions (eslint, vetur)
Do I have to create another issue ?

[electric-skeptic]

I'm sure we all have the same symptoms, as of the same version. Opening new issues divides the attention each issue gets, so it seems like we should contribute data to the same issue, otherwise devs get annoyed and close them as duplicates, which even the bot is noticing, or due to lack of further detail. We end up with the situation where people can see dozens of inadequately addressed, closed issues about this problem and are complaining about poor issue moderation instead of contributing to progress on it.
I'll stop trying to help so @mjbvz can pursue it with OP, but I'll definitely abstain from opening another issue about it.

[mjbvz]

Generic problems like this often have multiple different root causes and it is much easier for us to track each one individually. Otherwise we end up in exactly the situation we have now where multiple people chime in with +1 without providing any additional context and it is difficult to track their individual problems or follow up with them properly

So instead of complaining, please open a separate issue and share the logs on it as I requested

[brunoscopelliti]

I am sorry, I cannot share the log cause it is proprietary code.

[mjbvz]

@brunoscopelliti

1. Have you configured a custom TypeScript version in your workspace?
2. Are you loading a file on a network drive?
3. Does this happen for all projects?
4. If not, can you provide details on the type of project it does happen for
5. Can you share the last 20 or so lines of the logs