Cursor becomes ridiculously slow after a few hours of usage

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I open Cursor, it works fine - blazing fast.

But the longer I use it, the slower it gets. After just a few hours of use, it can’t even type; sometimes a letter appears 2 seconds after I press the keyboard. IDE becomes very laggy.

There’s no other way than to close the app and start it again - and then it’s fine again. But I have to do it 2-3 times per day - so seems like there’s a memory management issue.

I have a MacBook Pro M4 Max, so the hardware is definitely sufficient.

Steps to Reproduce

  1. Open Cursor
  2. Use AI agents
  3. The more you use it, the slower/laggier it gets
  4. Restart and repeat

Expected Behavior

It should work as fast as on the startup, even days or even weeks.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.29
VSCode Version: 1.105.1
Commit: 4ca9b38c6c97d4243bf0c61e51426667cb964bd0
Date: 2026-01-08T00:34:49.798Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.1.0

For AI issues: which model did you use?

Opus 4.5

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like

Hey, thanks for the report.

This looks like a memory leak or a process issue. Let’s check a few things:

  1. Extension Monitor: Settings > Application > Experimental > enable Extension Monitor, then CMD + Shift + P > Developer: Open Extension Monitor. Which extensions are using the most resources?

  2. Process Explorer: CMD + Shift + P > Developer: Open Process Explorer. Check the extensionHost and ptyHost processes when Cursor starts lagging. How much memory are they using?

  3. Quick test: Try running cursor --disable-extensions from a terminal and use it for a few hours. Does the issue still happen?

  4. MCP servers: Are you using MCP? There’s a similar issue where MCP processes keep piling up: MCP server processes are not terminated and accumulate over time, causing memory leaks

Also, please share:

  • Your codebase size
  • How many agent chats you have open
  • Whether you have a large chat history

This info will help the team narrow down the problem.

Thanks for a quick reply. I needed to restart Cursor to enable Extension Monitor, so I waited a bit for it to slow down again.

(“luckily” it slows down fast lol, already restarted 5 times today) :smiling_face_with_tear:

1. Extension monitor

2. Process explorer

extensionHost uses 406 MB, ptyHost 74 MB.

3. Cursor without extensions

Haven’t tried that one, but since usage is low, not even 1 GB, I don’t think it will have any effects.

4. I’m not using MCP.

5. Extra info

  • The codebase is massive - a big monorepo with 30-ish Next.js projects inside, plus 20-ish reusable packages. 850k+ lines of code (not counting node_modules and similar, with them is way more)
  • With agents, I sometimes have 2-3 running at the same time, but often only 1.
  • Chat history can sometimes be long, depending on the task/feature.
    • I keep the same agents running only if my prompts are related to the previous context. As soon as I’m done, a new chat is opened.
    • I also close chats now as soon as I’m done, but that doesn’t help.
    • Before, I never closed any chats - had tons of them at the same time - no problems.

Hope this helps!

Thanks for the screenshot. I can see <ext-host-runtime> is taking 99,64% of Extension Host time, that’s interesting.

A few questions and steps:

  1. Activity Monitor: Open Activity Monitor (macOS) and find the Cursor/Electron processes. What does memory usage look like when the IDE slows down? Extension Monitor shows only 326 MB, but real usage could be higher.

  2. Test without extensions: Given the size of your monorepo (850k+ lines), it’s worth testing. Run cursor --disable-extensions and use it for a few hours. This will help confirm whether the issue is tied to Extension Host or something else.

  3. .cursorignore: For a monorepo this large, I recommend adding a .cursorignore file to exclude unnecessary directories from indexing (node_modules, build artifacts, etc.). This can significantly reduce load.

This is a known issue for large codebases, and the team is working on optimizations. Let me know what you find from the tests.

Thanks for the info!

I updated .cursorignore, used it, no changes.

Unfortunately, today is a very bad day - Cursor gets very slow very fast - sometimes even after 10 minutes. It’s almost getting unusable at some point :frowning: take more than 5 seconds for text to appear on screen after typing. (everything else on my laptop works blazing fast)

I’ll try cursor --disable-extensions - last shot!

Here’s my activity monitor and all Cursor-related things:

1 Like

I see in your Activity Monitor screenshot that Cursor Helper (Renderer) is using 1.06 GB, which is a lot.

From your recent posts, it looks like things are getting worse, now it gets slow after about 10 minutes. This is a known issue with large monorepos, and the team is working on a fix.

Next steps:

  1. Test cursor --disable-extensions like you planned. This is the key test to see if the Extension Host is the cause.
  2. Can you share your .cursorignore contents? I want to make sure all the important directories are excluded (node_modules, .next, build, dist, etc.) for each project in the monorepo.
  3. What extensions do you have installed? (Settings > Extensions)

Temporary workaround while you test: if disabling extensions does not help, try working with one project at a time. Open a specific folder inside the monorepo instead of the repo root. This should reduce indexing load.

Waiting for the results from the no extensions test.

I’m so glad to hear they’re working on a fix!

Unfortunately, cursor --disable-extensions doesn’t make a lot of difference - I only have 7 basic extensions installed (image below).

Loading 1 project at a time is not really an option due to the monorepo architecture. Many projects are interconnected, and losing AI awareness over all of them would make things much slower.

I hope the team will fix it - it should be possible, especially because there’s a ton of free RAM & CPU to use. Good luck!