Hey @Francois1,
That dialog (reason ‘oom’, code -536870904) means the Cursor window’s own memory hit its built-in limit of roughly 4 GB per window, so it can happen no matter how much RAM the PC has. This is a known issue we’re already tracking, and I’ve added your report to it. It shows up most during very long agent chats: the window keeps a growing history of the agent’s file edits in memory, and reopens the same chat (and its history) after a crash.
In the meantime, these should make it much less frequent:
- Start a new chat regularly (for example once a day, or after a big task) instead of continuing one long chat. To bring context over, type @ in the new chat, pick Past Chats, and select the old one.
- Go to Cursor Settings > General > Startup and turn off Continue Interrupted Agents, so a crashed long chat doesn’t reload straight away.
- If you see the high memory warning, run Developer: Reload Window from the Command Palette before it crashes.
- Update to the latest version (Help > Check for Updates). Newer versions no longer keep full copies of very large files in the chat’s edit history.
On your data files: if the agent reads or edits them, adding those folders to a .cursorignore file keeps it away from them, which is worth doing. files.watcherExclude is fine to set too, but it isn’t what causes this particular crash.