Hey, thanks for the detailed report.
This is a known issue. Renderer crash (code 5) has been reported by multiple users on macOS ARM64 since the 2.6.x updates. You can see a related thread here: Cursor keeps crashing - 2.6.11. The team is aware and tracking it, but there’s no ETA yet. Your report helps with prioritization, especially since the Crashpad log pointing to mach_vm_read and process_memory_mac.cc narrows this down to a Chromium or Electron level issue on macOS.
I can see you’ve already tried pretty much every troubleshooting step. A couple of things that helped other users in similar cases:
-
Clear local databases. One user in the related thread said this fixed the crash:
# Quit Cursor completely first rm -rf ~/Library/Application\ Support/Cursor/IndexedDB rm -rf ~/Library/Application\ Support/Cursor/Local\ Storage rm -rf ~/Library/Application\ Support/Cursor/Session\ Storage rm -rf ~/Library/Application\ Support/Cursor/GPUCache rm -rf ~/Library/Application\ Support/Cursor/User/index -
Downgrade to 2.5.26 as a temporary workaround. Several users confirmed the crashes don’t happen on that version.
-
Your subfolder workaround is also valid and might be the least disruptive option for now.
About the cursor-socket missing out/ directory, we’re seeing this on other 2.6.x builds too. It’s a bundling issue on our side.
If you can share the main.log file (Help > Open Logs Folder) from around the time of a crash, that’d be helpful to pass to engineering.
Let me know how it goes.