High CPU usage by TypeScript language server. I have to restart TS server each time I launch Cursor to keep it normal

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I launch Cursor, it uses too much CPU and my laptop cooling running loud.
I remember that this issue was reported as Powershell related by someone else. But it wasn’t solved so I want to report it again.

The most interesting thing here that I can restart TS server and it’ll reduce the background CPU load significantly.

16% of CPU usage may seem like not a loot but it’s on i7 155h with 16 cores and 22 threads, the more threads the less percentage will be shown, and it definitely impacts cooling system and temperatures.

Steps to Reproduce

Just run Cursor and open JS or TS file to make language server run as well.

Expected Behavior

Low CPU usage when idle as it should be

Screenshots / Screen Recordings

This screenshot shows CPU usage when Cursor was ran without TS server restart.

The second screenshot shows reduced CPU usage after TS server restart.

So, I just ran Cursor, opened command palette and activated “TypeScript: Restart TS Server” and CPU utilization reduced significantly.

On both screenshots I didn’t do anything, just was looking into Task Manager to see CPU utilization when I do nothing to editor or opened files.

The TypeScript abilities remained untouched after restart so I can’t understand why I have more load at the beginning and less load after the restart.

It would be good workaround to set up auto restart for TS server on each launch but can’t do that. Maybe Cursor team can.)

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.33 (user setup)
VSCode Version: 1.99.3
Commit: a84f941711ad680a635c8a3456002833186c4840
Date: 2025-10-03T03:28:06.574Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

3 posts were merged into an existing topic: Powershell CPU utilization leak

Thanks for the report, I’ll merge this with similar reports and share it with the team.

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.