vscode: JS IntelliSense Loading Infinitely

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.65.2
  • OS Version: Windows 10 Pro 21H1 19043.1586

Steps to Reproduce:

  1. Open existing JS file or create and save new
  2. Look at infinitely loading bar

When I open JS file in VSCode it’s never completes IntelliSense loading.

photo_2022-03-17_22-05-08

Extensions list:

13xforever.language-x86-64-assembly
fabiospampinato.vscode-todo-plus
GitHub.github-vscode-theme
golang.go
GrapeCity.gc-excelviewer
icrawl.discord-vscode
ms-python.python
ms-python.vscode-pylance
ms-toolsai.jupyter
ms-toolsai.jupyter-keymap
ms-toolsai.jupyter-renderers
ms-vscode.vscode-typescript-next
rafamel.subtle-brackets

The bug is also reproduced with code --disable-extensions

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 4
  • Comments: 26 (7 by maintainers)

Commits related to this issue

Most upvoted comments

The tsserver at 1.65.2 is definitely leaking memory. This is the process invocation:

/opt/visual-studio-code/code \
    --ms-enable-electron-run-as-node \
    --max-old-space-size=8192 \
    /opt/visual-studio-code/resources/app/extensions/node_modules/typescript/lib/tsserver.js \
        --useInferredProjectPerProjectRoot \
        --enableTelemetry \
        --cancellationPipeName /tmp/vscode-typescript1000/6b96d5eb10edce778406/tscancellation-938f9057679d25ad026c.tmp* \
        --locale en \
        --noGetErrOnBackgroundUpdate \
        --validateDefaultNpmLocation \
        --useNodeIpc

The tsserver logs shows the that certain message getApplicableRefactors is never receiving response and always requested to be canceled. The process is getting abort signal when reaching the configured memory limits (tried 8gb!). Downgrading to 1.64.2 and the problem disappears. I think this is a bug.

@mjbvz I can confirm that problem disappears in previous 1.64.2

BTW tried also with nightly, same problem.

I found this report while searching on the issue myself. I only noticed it happening starting with 1.65 but no idea WHY it started happening. @Zx-EvM has provided more detail than I could have. I had initially tried disabling extensions as well with no change.

It looks as if @nati-maskens may have nailed it.

UPDATE: Just upgraded to 1.66 and the issue is still present. Spinner is still spinning on Loading IntelliSense status.