Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Very slow typescript autocomplete/intellisense #45433

Open
p32929 opened this issue Aug 2, 2021 · 7 comments
Open

Very slow typescript autocomplete/intellisense #45433

p32929 opened this issue Aug 2, 2021 · 7 comments
Assignees
Labels
Needs Investigation This issue needs a team member to investigate its status. Rescheduled This issue was previously scheduled to an earlier milestone

Comments

@p32929
Copy link

p32929 commented Aug 2, 2021

TS Template added by @mjbvz

TypeScript Version: 4.3.5

Search Terms

  • completions
  • intellisense

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

Steps to Reproduce:

  1. Open any NodeJS-TypeScript project
  2. Write the first letter of a class or variable
  3. Wait for the intellisense to show

Here's a screen record of the problem:
Vs

Version: 1.58.2 (user setup)
Commit: c3f126316369cd610563c75b1b1725e0679adfb3
Date: 2021-07-14T22:10:15.214Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Windows_NT x64 10.0.18363
Typescript version: 4.3.5

@mjbvz
Copy link
Contributor

mjbvz commented Aug 2, 2021

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

@p32929
Copy link
Author

p32929 commented Aug 6, 2021

Yes, even after disabling all the extensions, in the latest VScode

@outranker
Copy link

outranker commented Aug 7, 2021

@mjbvz you didn't request any info to further investigate the issue but labelled it as needs more info. is issue creator responsible for providing additional details about the performance problem after the issue is labelled?

@p32929
Copy link
Author

p32929 commented Aug 8, 2021

Is there any solution to this issue?

@mjbvz
Copy link
Contributor

mjbvz commented Aug 9, 2021

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 that file, it should contain perf information that can help us investigate the issue

⚠️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

@p32929
Copy link
Author

p32929 commented Aug 11, 2021

I will share the logs tomorrow

@p32929
Copy link
Author

p32929 commented Aug 12, 2021

tsserver.log
Here's the file. Hope it gets fixed soon. Thanks

@mjbvz mjbvz transferred this issue from microsoft/vscode Aug 12, 2021
@mjbvz mjbvz removed their assignment Aug 12, 2021
@RyanCavanaugh RyanCavanaugh added the Needs Investigation This issue needs a team member to investigate its status. label Aug 13, 2021
@RyanCavanaugh RyanCavanaugh added this to the TypeScript 4.5.0 milestone Aug 13, 2021
@RyanCavanaugh RyanCavanaugh added the Rescheduled This issue was previously scheduled to an earlier milestone label Dec 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Investigation This issue needs a team member to investigate its status. Rescheduled This issue was previously scheduled to an earlier milestone
Projects
None yet
Development

No branches or pull requests

5 participants