Hey @PerkyZZ,
Thanks for the screenshots, they help a lot. They show the CPU isn’t being used by Cursor’s own processes. Everything Process Explorer lists adds up to about 4% CPU and roughly 5 GB of memory, while your system is at 99%.
Process Explorer only shows processes that belong to the Cursor window that’s open right now, so the load is coming from something outside that list. Most likely it’s processes left over from an earlier Cursor session (for example MCP servers or tools that didn’t exit when Cursor closed or crashed), but it could be something else on the system.
Also, MCP may not be fully off yet. Servers that come with installed plugins (such as shadcn and Serena) are separate from the ones in your own MCP list, so please turn those off too to rule them out.
Next time CPU climbs, could you run these in a regular terminal and paste the output?
ps -eo pid,ppid,etime,pcpu,pmem,args --sort=-pcpu | head -20
- For the top three or four processes, run
ps -o pid,ppid,args -p PPID, using each one’s PPID from step 1, to see what started it.
- Quit Cursor completely (Ctrl+Q), wait 10 seconds, then run
pgrep -af -i 'cursor|bun|serena|uvx|npm exec'. Does anything still show up, and does CPU drop once Cursor is closed?
If Cursor closes on its own again, these would show whether Linux killed it:
journalctl -k -b | grep -i -E "out of memory|killed process"
journalctl --user -b | grep -i oom
coredumpctl list | grep -i cursor
Also, before reopening after a crash, zip the logs folder (Command Palette > Developer: Open Logs Folder) and attach it here.
In the meantime, if step 3 shows leftover processes, kill PID (or kill -9 PID if it ignores that) clears them, and logging out or rebooting clears them all.
On resetting Cursor: yes, you can test with a clean profile. With Cursor fully quit, rename the data folders instead of deleting them, so you can put them back:
mv ~/.config/Cursor ~/.config/Cursor.backup
mv ~/.cursor ~/.cursor.backup
Then start Cursor and sign in again. It will start with default settings, no extensions, and no local chat history. If the problem goes away, the cause is in your old profile. If it doesn’t, rename the backups back to restore everything. I’d do the process check above first, though: since Cursor’s own processes look quiet in your screenshot, a reset may not change much.