Window crashed when model generate plan with plan mode

[AmbitionsXXXV (Et cetera)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Currently, when I use plan mode, when the model starts editing the plan, the CPU load suddenly jumps to two or three times the normal speed, and then the IDE window crashes.

This has wasted 7 or 8 of my requests.

Steps to Reproduce

run plan mode with gpt-5.2-xhigh model. and the model is generate Plan MD

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.4.2
VSCode Version: 1.105.1
Commit: 7d37854462030d31d936c7f7ed9015b870551e90
Date: 2026-01-20T06:54:16.351Z
Build Type: Stable
Release Track: Early Access
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0

For AI issues: which model did you use?

Model: gpt-5.2-codex-xhigh

For AI issues: add Request ID with privacy disabled

last request id: d028c5f8-4e70-4225-a259-f2b031398d40

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the report and for sharing the request ID.

This looks like a plan rendering or UI issue during generation, especially given the sudden CPU spike. There’s a similar known issue here Planning next moves stuck with UI stuttering while generating markdown tables or diagrams, but your case looks more severe since it’s a full crash.

I’ll need a bit more info to troubleshoot:

• Console logs: Go to Help > Toggle Developer Tools > Console. Please take a screenshot of any errors right when it crashes.
• Extensions check: Try running cursor --disable-extensions in the terminal and repeat the plan generation. Does it still crash?
• Repro: Does this happen every time in plan mode, or only sometimes? Does it depend on the plan size or complexity?

Workaround for now: Try a different model instead of gpt-5.2-codex-xhigh (for example, Sonnet 4.5 or GPT 5). It might be specific to that model and the kind of plan it generates.

Let me know what you find.

[AmbitionsXXXV (Et cetera)]

• I’ve update cursor to version 2.4.7 still got this issue
• this is actually happens every time in plan mode
• and I tried switch to opus4.5. Also get window crashed
• also crashed with cursor --disable-extensions
• from the console after shows the warning msg the window is getting crashed.This time it’s even worse; the application becomes unresponsive and requires a forced exit.
  
• Some more request attempts were wasted.

[AmbitionsXXXV (Et cetera)]

Then some additional cases
Maybe I just open 4 or 5 window, the CPU LOAD get MAX. Then make cursor app not responded.
And just open window.
My machine is Mac 48G ram M4 pro.

[deanrie]

I see the screenshot with the MTLReporter errors. This looks like a UI rendering issue during plan generation.

The team is aware of this Plan mode issue. From the console logs, it looks like the markdown renderer is what’s crashing. This matches a known bug where generating tables or charts can make the UI lag and then crash.

To better understand your case, can you share:

• The full log from Developer Tools (Help > Toggle Developer Tools > Console). Please include everything around the crash, not just a screenshot
• CMD + Shift + P > Developer: Open Process Explorer. Please send a screenshot right before the crash so we can see which process is using CPU
• How big or complex are the plans you’re generating. Do they include tables or charts?

Workaround for now: use Ask or Agent mode instead of Plan mode. Rendering is usually more stable there.

About multiple windows, yes, that can make it worse. Try starting with just one window.

Let me know if you find anything else.

[AmbitionsXXXV (Et cetera)]

after I upgrade cursor to version 2.4.18

cursor.txt (29.0 KB)

and the log is in the attachment

[deanrie]

Thanks for the logs. The key issue here:

[RPCProtocol] Pending RPC count (100000) exceeded threshold 100000
ExtHostCursor.$getMetricsProviderDistribution: 99969

You’ve built up almost 100,000 pending RPC calls from the metrics collection system. That’s an infinite loop. Because of that, Composer can’t get the first token (it times out after 10 seconds), CPU usage spikes, and everything crashes.

This looks like a regression in 2.4.x. I’ll pass it to the team.

Temporary workaround:

• Use Ask or Agent mode instead of Plan mode. This issue doesn’t trigger there.
• Close extra Cursor windows (you mentioned 4 to 5). Each one adds more load.

Could you share a bit more info:

• What exactly is Plan doing when it crashes. Is it generating tables, diagrams, or a lot of code?
• Does it reproduce in a new empty project, or only in your current workspace?

Let me know if you find anything else, or if the workaround helps.

[AmbitionsXXXV (Et cetera)]

yes,both new empty project and current workspace
And when I just work with one window in plan mode, also get the crash

[deanrie]

Thanks for the detailed logs. I’ve shared the infinite loop bug in metrics collection with the team. It’s a regression in 2.4.x.

Right now there’s only one workaround: use Ask or Agent mode instead of Plan mode. The issue doesn’t trigger there.

As soon as there’s a fix, we’ll update the thread. Sorry for the inconvenience. Plan mode is indeed broken in your case.