Persistent Crashes and Timeouts!

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Keeps Timing out and asking to try again but the partial code it tried to build are still counted in usage! Is there some kind of “Rush Hour” when too many users are working with Cursor that I should stay away from?

Steps to Reproduce

Do anything in the middle of the day!

Screenshots / Screen Recordings

Cursor timeouts.jpg
Cursor timeouts.jpg862×199 24 KB

Operating System

Windows 10/11

Version Information

Version: 2.5.17 (user setup)
VSCode Version: 1.105.1
Commit: 7b98dcb824ea96c9c62362a5e80dbf0d1aae4770
Date: 2026-02-17T05:58:33.110Z
Build Type: Stable
Release Track: Default
Electron: 39.3.0
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

3

Hey, based on the screenshot it looks like a Provider Error. This was a widespread issue on February 19, and several users reported the same thing.

A couple things to try:

  1. Cursor Settings > Tools & MCP: if you have any MCP servers connected, temporarily disable them all. This fixed it for most users with this error.
  2. Cursor Settings > Models: make sure “Override OpenAI Base URL” is turned off, and remove any third-party API keys if you added them.
  3. Network settings: go to Settings > Network and try enabling “Http Compatibility Mode” (disables HTTP/2). This helped another user: thread (Again We're having trouble connecting to the model provider. This might be temporary - please try again in a moment).
  4. Try switching to a different model for now. Some models were impacted more than others.

Which model were you using when this happened? And do you have any MCP servers set up?

4

Did that but now keeps crashing the actual application

image
image911×316 14.4 KB

5

I see the screenshot. This is an OOM crash (out of memory), error code -536870904. It’s a different issue and not related to the provider errors from the previous post.

On Windows, Cursor’s renderer can hit a ~4 GB memory limit (an Electron limitation). With long chats or agent sessions, that can lead to a crash.

What you can do:

  1. Rotate chats: Don’t work in one very long chat. Start a new chat regularly, especially before big tasks.
  2. Monitor memory: Press Ctrl+Shift+P then Developer: Open Process Explorer. Watch the renderer process. If it’s getting close to 3.5 GB, it’s time to start a new chat.
  3. Check extensions: Try launching from the command line with cursor --disable-extensions. Some extensions can significantly increase memory usage.
  4. Clear chats: If it crashes right on startup, delete older chats via the Chat History panel.

Also check the console: Ctrl+Shift+P then Developer: Toggle Developer Tools then Console. Do you see lines like [otel.error] or OTLPExporterError? If yes, that can point to an additional memory leak.

More details here: Cursor crashes repeatedly with out-of-memory (OOM) errors after the latest update, especially during large prompts or long-running plans

Let me know if this helped.