Topic clusters
Why is Cursor using so much RAM on a Mac?
Short answer: Cursor is many processes, not one, and the big ones are usually the extension host, the language server or a window that has been open for days. Here is how to tell which, and what is safe to restart.
Cursor is built on the same Electron foundation as Visual Studio Code, so one running Cursor is really a group of processes: a main process, one renderer per window, an extension host that runs your extensions, a shared process, a file watcher, a terminal host, and a language server for each language that has one. Activity Monitor lists each of them separately, which is why "Cursor" can look like it is using several gigabytes while no single line looks alarming.
A big Cursor is not automatically a problem. What matters is whether your Mac is short of memory, and whether Cursor's memory keeps growing while your work stays the same. This guide checks both, then goes from the least disruptive fix to the most. Everything here works without installing anything.
Step 1: Check whether your Mac is actually short of memory
macOS fills spare memory with cache on purpose, so a high "Memory Used" number proves nothing. The signal is memory pressure: green is fine, yellow means macOS is compressing memory to make room, red means it is leaning on disk. Run these two commands in Terminal.
If pressure is 1 (normal) and swap is small, Cursor is not what is slowing your Mac. Look at CPU instead, or at your disk. If pressure is 2 or 4, or swap keeps growing while you work, carry on.
sysctl -n kern.memorystatus_vm_pressure_levelsysctl vm.swapusageThe output looks like total = 17408.00M used = 16339.12M free = 1068.88M. Swap that grows steadily while you work is the sign of real shortage.
Step 2: Find which Cursor process is the big one
In Cursor, open the Command Palette (Shift-Command-P) and run Developer: Open Process Explorer. It lists the editor's processes with their memory, and names each window and extension host by project. This is the quickest way to see which window or extension is responsible.
From Terminal, you can sum Cursor's memory and list its largest pieces. Both commands print only process names and sizes, never your project paths or command lines.
footprint $(pgrep -f "/Applications/Cursor.app/")The first column of the TOTAL row is dirty memory: memory the processes have changed, including what macOS has compressed or moved to swap. It is usually larger than the resident sizes ps shows, and it is what actually competes with your other apps for RAM.
ps -axo rss=,etime=,comm= | grep -i "Cursor" | grep -v grep | sort -rn | head -10The first column is resident memory in kilobytes. A renderer or extension host that has been running for days is the first suspect.
What is normal and what is not
Normal: a second or two of extra memory when you open a large project, a language server that grows while it indexes and then settles, and a renderer that holds more when you have many tabs or a long AI chat open. A few gigabytes across all Cursor processes on a large project is ordinary on a modern Mac.
Not normal: memory that climbs steadily for hours while you do the same work, an extension host far larger than its neighbours, or a single window holding far more than your other windows. Those point to a leaking extension, a language server that has outgrown its limits, or a very long session. A process that is large but stable is not a leak, and restarting it only costs you a warm-up.
Step 3: Fixes, from least to most disruptive
Try these in order and check memory after each. Save your work first; none of them should lose unsaved editor content, but terminals and running tasks inside the window restart when you reload it.
- Restart the language server. For TypeScript and JavaScript projects, run TypeScript: Restart TS Server from the Command Palette. Autocomplete pauses for a few seconds while a fresh server starts.
- Cap the TypeScript server. Add
"typescript.tsserver.maxTsServerMemory": 4096(megabytes) to your settings if one project's server keeps outgrowing its share. It stops the server growing without limit, and the editor restarts it when it hits the cap. - Stop watching dependency and build folders. In settings, add
node_modules,dist,buildand.nexttofiles.watcherExcludeandsearch.exclude. Less to watch means less background work and memory. - Find a leaking extension. Run Developer: Show Running Extensions to see which extensions are active, or Help: Start Extension Bisect to disable half of them at a time until the growth stops.
- Reload the window. Developer: Reload Window gives that window fresh helper processes without closing the app.
- Quit and reopen Cursor. If you keep many project windows open for days, this clears all of it at once. Windows are restored when you reopen.
A checklist that works without any app
1. Pressure normal and swap small: stop, Cursor is not the problem. 2. Otherwise open Process Explorer and note the biggest window or extension host. 3. Restart the TS server, then reload that window. 4. Add watcher excludes for dependency folders. 5. Bisect extensions if one process keeps growing. 6. Quit and reopen Cursor once a day if you leave projects open overnight.
Worth knowing: Cursor is rarely the only large thing. AI coding tools start helper processes of their own, and other apps, Docker and local models add up. The memory snapshot we took of a real developer Mac shows how the pieces add up, and the free check script lists them for your Mac in one run.
When to let an app do it
If you would rather not repeat this by hand, Sentinely does the same check in a few seconds. It watches memory pressure and swap, names the editor windows, language servers and leftover helpers that are holding memory, shows what a fix will cost before it runs, and measures what came back. The diagnosis, warnings and your first fix are free. If your Mac is fine, it says so.
Questions
Why does Cursor use so much memory on a Mac?
Cursor runs as a group of processes: a renderer per window, an extension host, a file watcher, a terminal host and language servers. Together they can hold several gigabytes on a large project, and long sessions make them grow. Check memory pressure first. If it is normal, a big Cursor is not the cause of a slow Mac.
Is it a memory leak if Cursor keeps growing?
Only if memory climbs steadily for hours while your work stays the same. Growth that settles after indexing or after opening a large project is normal. A single extension host or language server that keeps growing points to a leaking extension or an over-large project, and restarting it is safe.
How do I see which Cursor process uses the most memory?
Run Developer: Open Process Explorer from the Command Palette, or run footprint $(pgrep -f "/Applications/Cursor.app/") in Terminal for the total and ps -axo rss=,etime=,comm= | grep -i Cursor | sort -rn | head for the biggest processes.
Is it safe to restart Cursor's language server or extension host?
Yes. TypeScript: Restart TS Server only pauses autocomplete for a few seconds, and Developer: Reload Window restarts the extension host. Save your work first, because terminals and running tasks in that window restart.
Will adding more RAM fix it?
It helps if memory pressure is high and swap keeps growing, because macOS then has room to keep everything in memory. It does not fix a leak. A leaking process grows into whatever space it is given.