OOM Error on 2.6.0

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After opening a project in Cursor, I get an OOM error code -568

Steps to Reproduce

Launch Cursor, open a project, wait a minute or two.

Expected Behavior

Cursor doesn’t close unexpectedly.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 2.6.0-pre.30.patch.0 (user setup)
VSCode Version: 1.105.1
Commit: b7f1857a3b35e0b1f03073389bd4bfc4c43d0ef0
Date: 2026-02-22T23:27:20.837Z
Build Type: Stable
Release Track: Nightly
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like

Hey, thanks for the report. OOM crashes on Windows are a known issue. The Electron renderer process hits the memory limit and crashes.

A couple of quick questions so we can understand the scope:

  1. Does it crash right when you open the project (without using Agent chat), or only after you send messages in chat?
  2. Can you reproduce it on the stable build (not Nightly)?

Workarounds to try:

  • If you use Agent chat, rotate chats. Don’t keep very long sessions, start a new chat when the current one gets large.
  • Press Ctrl+Shift+P then Developer: Toggle Developer Tools then open the Console and check if you see lines like [otel.error] or OTLPExporterError. If yes, that can be an extra memory leak.
  • Press Ctrl+Shift+P then Developer: Open Process Explorer to track which process is using the memory.

Since you’re on Nightly, please try switching to the stable branch and see if the issue still happens. That’ll help confirm whether this is a regression in 2.6.0.

The team is aware of this issue. Let me know the answers to the questions above.

1 - crashes when i open the project, no agent chat is loaded, i just wait two minutes after opening and it crashes, there’s no action on my part.

no otel or otlp console errors

nothing seems to spike memory usage, it tripped around 1.5GB RAM usage

2 - changed to the stable build (details below), no OOM error on initial project load

Version: 2.5.20 (user setup)
VSCode Version: 1.105.1
Commit: 511523af765daeb1fa69500ab0df5b6524424610
Date: 2026-02-19T20:41:31.942Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

2 Likes

Well it looks liek you’re not on 2.6 rather 2.5.20, but I am on 2.6.x and oom crashes a plenty.

Version: 2.6.0-pre.33.patch.0 (user setup)
VSCode Version: 1.105.1
Commit: 3a1ff150ed66f295af45ae38f28f6afaa05a4770
Date: 2026-02-23T23:34:26.530Z
Build Type: Stable
Release Track: Nightly
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26300

Correct; following the instructions provided, I downgraded to the stable build from nightly, which solved the problem.

1 Like

oh I’m stupid, I missed that part lol. ok ok so that one works for you, I might have to try that… Thanks!

I just checked on this, the stable build does not crash but the nightly build is still crashing with the OOM error.

Version: 2.7.0-pre.1.patch.0 (user setup)
VSCode Version: 1.105.1
Commit: 34b7632f678a798c01a485eefc64b5c5f156eef0
Date: 2026-02-26T19:48:07.357Z
Build Type: Stable
Release Track: Nightly
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

Now getting the OOM error on the stable build

Version: 2.6.11 (user setup)
VSCode Version: 1.105.1
Commit: 8c95649f251a168cc4bb34c89531fae7db4bd990
Date: 2026-03-03T18:57:48.001Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

Latest stable build update is still throwing the OOM error.

Version: 2.6.12 (user setup)
VSCode Version: 1.105.1
Commit: 1917e900a0c4b0111dc7975777cfff60853059d0
Date: 2026-03-04T21:41:18.914Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

So is this something I can expect to get fixed? Or should I just cancel my sub bc this is unusable?

Tried running with gpu disabled and extensions disabled, still getting the OOM.

Canceling my sub since it appears there’s no fix in sight. Really disappointed

Version: 2.6.13 (user setup)
VSCode Version: 1.105.1
Commit: 60faf7b51077ed1df1db718157bbfed740d2e160
Date: 2026-03-06T06:17:49.499Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

Checked again after the update this morning, still failing.

Version: 2.6.14 (user setup)
VSCode Version: 1.105.1
Commit: eb1c4e0702d201d1226d2a7afb25c501c2e56080
Date: 2026-03-08T15:36:54.709Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

It may be resolved? I was able to open the repo and complete a chat session today for the first time in a week

Version: 2.6.18 (user setup)
VSCode Version: 1.105.1
Commit: 68fbec5aed9da587d1c6a64172792f505bafa250
Date: 2026-03-10T02:01:17.430Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045