High CPU usage by typescript-language-features (built-in ext) in Windows when idle

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Lately my laptop stays hot with Cursor open when I don’t do anything.

In the task manager, I saw powershell+conhost executed again and again (almost every second) by Cursor with the following command line:

powershell.exe -c gwmi win32_process -Filter 'ProcessId=21096 or ProcessId=9804' | select CreationDate,KernelModeTime,ParentProcessId,ProcessId,UserModeTime,WorkingSetSize | format-table

ProcessIds were different between launches. The CPU column in the task manager showed values anywhere between 0.01 and 20%.

I grep’d Cursor files for the string CreationDate,KernelModeTime,... and found it in \AppData\Local\Programs\cursor\resources\app\extensions\typescript-language-features\dist\extension.js. Then I checked the same extension in VS Code and couldn’t find that string. After that I replaced the Cursor’s extension.js with the “same” file from VS Code and the problem was gone without any apparent side effects. When I swapped the files back, the problem reappeared.

Thus, my conclusion is that there’s a bug in the built-in extension “typescript-language-features”. Its Cursor variant, to be exact.

Steps to Reproduce

Open a TypeScript project in Cursor.

Screenshots / Screen Recordings

2025-10-17_17-21-24.png
2025-10-17_17-21-24.png1055×566 233 KB

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.46 (user setup)
VSCode Version: 1.99.3
Commit: b9e5948c1ad20443a5cecba6b84a3c9b99d62580
Date: 2025-10-14T01:21:46.830Z
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

Sometimes - I can sometimes use Cursor

2

Hey, thanks for the report. You’ve clearly identified a regression in Cursor’s typescript-language-features extension that causes repeated PowerShell process spawns.

I’ll pass this to the team. The fact that swapping in VS Code’s version fixes it confirms it’s Cursor-specific.

Temporary workaround: as you found, replacing the extension.js file with VS Code’s version resolves it, but you’ll need to redo this after Cursor updates.

4

Yep, that’s what I had to do today.

1 Like
5

I don’t have this issue anymore in up-to-date Cursor.

1 Like