Hey, this is a known class of bugs. On Windows, the renderer process hits the ~4 GB V8 heap limit and crashes with code -536870904. A few root causes are already being tracked internally, but there’s no ETA for a fix yet.
The main thread with details and a repro is here: Renderer OOM crash (code -536870904) every ~3 minutes on Windows — 128GB RAM, reproducible
What you can try for now:
- Don’t keep terminal + browser + file reader open in the sidebar at the same time. That combo is what spikes memory in your case.
- Periodically close or clear the terminal if it has a lot of output.
- If it’s too disruptive, stay on 3.2.16 since it’s stable for you.
About the app not launching from the icon after a crash. That can happen if the OOM corrupts state.vscdb. Try closing all Cursor processes in Task Manager and relaunching. If that doesn’t help, you can temporarily rename %APPDATA%\Cursor\User\workspaceStorage. This will reset workspace state, but your settings and chats will remain.
Let me know if it still crashes after these workarounds and we’ll collect logs.