Keeping the Cursor App Stable
The Cursor app has implemented new systems to enhance stability and reduce crashes. Recent efforts have led to an 80% decrease in out-of-memory (OOM) errors per session. The team employs dual debugging strategies to identify and address the root causes of instability.
- ▪The app's OOM-per-session rate has fallen 80% since its peak in late February.
- ▪Crashes are primarily caused by the app running out of memory, particularly in renderer processes.
- ▪The team uses telemetry to track crash events and has developed metrics to monitor app stability.
Opening excerpt (first ~120 words) tap to expand
Blog / researchApr 21, 2026·researchKeeping the Cursor app stableAndrew Chan & Kevin Nguyen · 8 min readTable of Contents↑Detecting and measuring instabilityDual debugging strategiesTop-downBottom-upTargeted mitigationsPreventing regressions, staying fastStability for a new generation of softwareMany of our users spend their entire day using Cursor, which means even rare crashes can be extremely disruptive. At the same time, the challenge of keeping the app stable has grown as we've added users and shipped increasingly ambitious features like subagents, instant grep, browser use, and more. Most of these crashes are caused by the app running out of memory (OOM).
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Cursor.
Discussion
0 commentsMore from Cursor
