Curosr 2.7.0.pre76 stuck all the time

Support Bug Reports
, ,
1

Describe the Bug

It stucks during thinking. App does not responsive.

Steps to Reproduce

upgrade to 2.7.0 pre76

Expected Behavior

App should work

Operating System

MacOS

Version Information

2.7.0-pre76

Does this stop you from using Cursor

Yes - Cursor is unusable

3

image
image1948×488 104 KB

image
image600×732 46 KB

Is there easy way to downgrade to the previous nightly? I do not have the previous version and

5

Hey, I can see from the screenshots that the renderer is at 519% CPU and the crash code is 5. This is a known issue on macOS that affects multiple versions starting from 2.5.26.

To get back to a working state, the easiest option is to switch to Stable. Go to Cursor Settings > Beta, select Default, then restart. Nightly doesn’t have a built-in way to roll back to an earlier Nightly build.

If you want to stay on Nightly, a few things that can help reduce crashes:

  • Keep only one Cursor window open at a time. More windows usually means a faster crash.
  • Start fresh chats sometimes instead of keeping very long ones.
  • Run with extensions disabled: cursor --disable-extensions
  • Disable GPU: cursor --disable-gpu

The team is aware of this. It’d also help a lot if you can grab main.log from Cmd+Shift+P > Developer: Open Logs Folder around the time of the next crash. That’ll help narrow down the root cause.

1 Like
6

I would suggest to allow users to download nightly version they want (show full list), eg. do not limit to the last one.

Another question I have in mind. Nightly version could have chat history incompatibility, thus when I install stable it could say that chat format is broken, Right?

Overall I like the Cursor, if I compare it to the version in Jan 2026, today it is much much better. Keep going! Thanks.

7

Glad to hear you’re enjoying Cursor overall!

On your questions:

  1. Nightly version picker: totally fair request. Right now there’s no way to pin or pick a specific nightly build, but I’ll pass the feedback along. It’d definitely help when a build breaks something.

  2. Chat history when switching to Stable: your chat history should generally carry over. That said, chats created on a newer nightly build might not render perfectly on an older stable version since the internal format can change over time. It shouldn’t break Stable itself, but some individual chats might look a bit off or lose context. If you notice anything weird, starting new chats on Stable is the safest bet.

Let me know if you run into anything after switching!

1 Like
8

I mentioned chats, because when I tried 2.5+ version and then install again stable 2.3. Chats that were created by 2.3 also became inaccessible. Thus I am worrying that new version should not convert the old chats to new format automatically.
Otherwise it looks good.

1 Like
9

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.