-
Notifications
You must be signed in to change notification settings - Fork 12.8k
High CPU and memory usage on tsserver #26968
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
Comments
@Maistho Can you please describe the general structure of your project. Do you have jsconfig.json or tsconfig.json files? About how many js/ts files do you have? @sheetalkamat I don't see anything suspicious in the logs. The last line is:
|
Since the project was opened with projectRootPath as |
@mjbvz I have 3+ tsconfig.json files, and a bunch of data files in a ignored directory. Amount of js/ts files is a couple hundred. @sheetalkamat Thanks for the quick reply! Using the latest version of vscode seems to solve the issue! What I did:
Then in vscode "typescript.tsdk": "./node_modules/typescript/lib" |
Probably #25811 fixed this. |
I have been having this issue for months now, and sometimes it goes away with a restart. It occurs with all extensions disabled. Running latest OSX and latest non-insiders build. I have produced a This is not limited to just one project though. |
@alexmccabe Can you please open new issue with your repro details. You can share log confidentially on Microsoft servers if your company allows that. You can upload logs by following these steps:
We also have process to sign NDA if that's what is needed to look into repro, but tsserver log can be good first starting point of investigation. |
From @Maistho on September 7, 2018 21:16
Steps to Reproduce:
The offending process has the following commandline:
Does this issue occur when all extensions are disabled?: Yes
I have uploaded logs from my session with the following ID:
Log file ID: 3308023914
Let me know if there's anything I can try to debug this.
Copied from original issue: microsoft/vscode#58223
The text was updated successfully, but these errors were encountered: