Cursor consumes a lot of memory

Support Bug Reports
1

Describe the Bug

See the screenshot

image
image1920Ă—1457 238 KB

Steps to Reproduce

NA

Expected Behavior

It should not consume so much

Operating System

MacOS

Version Information

v3.1.0 pre 12

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Same here. The memory leaks are insane. Multiple times a day it’s completely freezes my entire Mac.

I don’t agree that I can continue to use cursor with this bug. I can’t use anything when this happens.

For me, it seems to be related to the Go language server inside cursor while a separate process is making a lot of changes to Go files. Just a hunch though. I can’t actually diagnose because when this happens everything freezes.

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.

8

That is not possible. when this happens only “FOrce quit appication” is available.