Cursor consumes a lot of memory

Support Bug Reports
7

Hi @Eugen_Konkov,

Thanks for reporting this. Memory consumption issues like this are a known problem our team is tracking.

115 GB is extreme – to help narrow down the cause, could you provide two things?

  1. Process Explorer output: Cmd+Shift+P > “Developer: Open Process Explorer” – this shows which specific process is consuming memory

  2. Terminal check for orphaned processes:

ps aux | grep "Cursor" | grep -v grep

Workarounds in the meantime:

  • Fully quit Cursor with Cmd+Q (not just closing windows) and relaunch – this cleans up all child processes

  • Start fresh chats periodically rather than continuing very long conversations

  • If you’re on Nightly, consider trying Stable to see if the issue persists

A user in this related thread saw the same pattern – Force Quit showed 113 GB but Process Explorer showed only ~300 MB. The gap was caused by orphaned helper processes that macOS counts under Cursor but aren’t visible to the editor itself.

@rmgn - The Go language server hint is useful. If you’re able to check Process Explorer next time it happens, that would help confirm whether the language server is the specific culprit.