with the latest update to Cursor, I get a frequent OOM crash. Is there a way for me to revert to previous version of Cursor? This was not the issue before, its new.
Hey, thanks for the report. This is a known Windows issue where the renderer process in Cursor hits a ~4 GB memory limit (an Electron limitation on Windows).
I would be interested in this too. I need to restart Cursor every 20-30 minutes or so when working intensively, or it just crashes.
I get tons of otel.error OTLPExporterError messages stating, “Trace spans collection is not enabled for this user”.
I see no option to disable the telemetry services so these errors just fill up the memory, I guess.
So, I have seen in the topic to fall back manually to 2.3.34 but from official Cursor 2.3 downloads I can only get 2.3.35 and found no official source for 2.3.34 on Cursor.com.
Anyone with a valid official download link for this?
Any ideas when this is going to get fixed? It renders the app next to useless and a real time robbery.
Dean, It appears that Electron memory limit per renderer process (since v14+) is now 8MB. it won’t solve the underlying problem, but to gain an extra few minutes between crashes would be helpful.
Hey user376, been there. You can actually give the renderer more breathing room by launching Cursor with the , max-old-space-size=8192 flag. This usually stops it from crashing during heavy lifts. It also helps a ton to add things like node_modules or build folders to your .cursorignore file. That keeps the AI indexer from trying to scan everything, which saves a lot of memory.
