Window Terminated Unexpectedly

Support Bug Reports
,
1

Keep getting this once I try to execute plan mode - have 64gb of RAM, not sure if it’s actually OOM.

image
image839×521 5.13 KB

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

4

Hey, thanks for the report.

A couple of things to start with:

  1. Check for an OTEL memory leak: Ctrl+Shift+P > Developer: Toggle Developer Tools > Console. If you see errors like [otel.error] or OTLPExporterError, that’s a memory leak that started in version 2.3.35.

  2. Workarounds:

    • Chat rotation: start a new chat before big plan mode tasks, don’t keep everything in one chat
    • Watch memory: Ctrl+Shift+P > Developer: Open Process Explorer. If the renderer is getting close to 3.5 GB, it’s time to start a new chat
    • Try cursor --disable-extensions to rule out extensions

Also, please share your Cursor version (Help > About Cursor). If you’re on 2.3.35+, it might be worth rolling back to 2.3.34.

5

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.