Skip to content

TSServer High CPU usage #31248

Closed
Closed

Description

@kasik96
  • VSCode Version: 1.32.3
  • OS Version: Fedora 29

Steps to Reproduce:

  1. Install clean stable VSCode with neo extensions or setting
  2. Open large project with sub projects
  3. Check System Monitor -> HIGH CPU Usage, almost non usable OS

I tried to turn off some settings, but nothing help.
It caused by TSServer.js build-in "TypeScript and JavaScript Language Features" extension.

Solution: Disable "TypeScript and JavaScript Language Features" build-in extensions.

Screenshot from 2019-03-21 11-18-59
Screenshot from 2019-03-21 11-19-27
Screenshot from 2019-03-21 11-19-56

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

Activity

  1. mjbvz commented on Mar 21, 2019

    @mjbvz

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

  2. kasik96 commented on Mar 21, 2019

    @kasik96
    Author
  3. kasik96 commented on Mar 21, 2019

    @kasik96
    Author

    Also i have the same problem with Ubuntu (Unity, XFCE), Mate and Fedora.

  4. kasik96 commented on Mar 26, 2019

    @kasik96
    Author

    Matt Bierner (@mjbvz) Any update on this bug? Also tested on Manjaro, i have same problem. It does not look it happens on Windows, it has little more CPU use, but not that much as in Linux.

  5. ZachGoldberg commented on Apr 16, 2019

    @ZachGoldberg

    Same here. Ubuntu 18.04. Identical symptoms. Disabling JS & TS features built-in also fixes it.

  6. abhishek-rs commented on Apr 18, 2019

    @abhishek-rs

    Have the same issue on MacOS Mojave. Using this as a workaround -

    1. Disable the default javascript validation -
      "javascript.validate.enable": false
    2. Use the external ESLint extension - https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint
  7. mjbvz commented on Apr 18, 2019

    @mjbvz

    Martin Kase (@kasik96) 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 folder with a tsserver.log file in it

    If you can share the log, I can also take a look to see if anything stands out that could be causing this

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

  8. kasik96 commented on Apr 18, 2019

    @kasik96
    Author
  9. stefems commented on Apr 24, 2019

    @stefems

    +1
    I'm having the same cpu issue with eletron_node tsserver.js as shown in the vs code process explorer. Pls fix soon. My laptop has been melting my fingers. Suggestion by abhishek-rs has been working thus far.

  10. npesa92 commented on May 1, 2019

    @npesa92

    +1 Having the same issue here. One line change will spike CPU and show electron_node tsserver.js as the problem

  11. SeedyROM commented on May 3, 2019

    @SeedyROM

    +1 Can confirm on Ubuntu 16.04, problem seems to be stemming from tsserver. I have nearly identical logs to kasik96. Use an older version of VSCode in the mean time instead of trying to hack this into working!

  12. mjbvz commented on May 4, 2019

    @mjbvz

    Moving this upstream as I don't see anything that stands out in those logs.

    Can you please try upgrading your workspace to use typescript@next by following these instructions just to make sure this hasn't already been fixed

  13. removed their assignment
    on May 4, 2019
  14. 34 remaining items

  15. added
    Needs InvestigationThis issue needs a team member to investigate its status.
    and removed
    Needs More InfoThe issue still hasn't been fully clarified
    on Oct 29, 2019
  16. arielsalminen commented on Dec 21, 2019

    @arielsalminen

    Have been facing this exact issue as well on the latest macOS for the past few weeks and haven’t been able to solve it.

  17. sheetalkamat commented on Jan 30, 2020

    @sheetalkamat
    Member

    @cushmatt can you please try typescript@next to see if the issue still repros.. We made some changes to directory watching for Linux and it might have fixed the issue with the files being watched..
    If the issue still repros, please share new tsserver log with the latest build when the issue repros to be able to investigate this further

  18. added
    Needs More InfoThe issue still hasn't been fully clarified
    and removed
    Needs InvestigationThis issue needs a team member to investigate its status.
    on Jan 30, 2020
  19. m0xj commented on Apr 22, 2021

    @m0xj

    I am still experiencing this issue with VSCode Insider and typescript@next.

  20. mjbvz commented on Apr 23, 2021

    @mjbvz

    @puppeteer701 Please open a new issue with information about your project

    Closing this since we cannot investigate this without more info from the original poster

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Domain: PerformanceReports of unusually slow behaviorNeeds More InfoThe issue still hasn't been fully clarified

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions