cursor
cursor copied to clipboard
MacOS 26 (Tahoe) lag due to electron bug
Latest Cursor is using Electron version 34.5.8. There was a bug fixed in electron that affects MacOS 26 (Tahoe) and Cursor needs to update the electron version in order to get this fix.
The specific Electron versions that contain the fix for the issue are v39.0.0-alpha.7, v38.2.0, v37.6.0 and v36.9.2.
This issue was fixed in VS Code (see https://github.com/microsoft/vscode/pull/269279) and released as part of the September 2025 release (VS Code versions 1.105.0 or 1.105.1, haven't determined which yet). Perhaps the team can update the VS Code engine this is built on to the latest OR merely update electron to v37.6.0. Either would solve this.
This issue is fairly detrimental (even though there is a very hacky workaround) and should be prioritized.
Even in the Early Access or Nightly beta versions, this is not fixed.
Great news everyone, 1.9.0-pre.1.patch.0 is available via Nightly which fixes the issue!
Big thanks to @tmm1 and Cursor Team. The hotfix via koffi is first of its kind and I've not seen any other company do it except cursor. But it works!
Spoke too soon, this fix is gated to 25.0.* only for some reason.
This bug exists in MacOS Kernel version 25.0.* and 25.1.*
Come on guys :(
Good catch. It does work on latest stable Tahoe though, that's where we tested it.
> parseFloat('25.0.1')
25
> parseFloat('25.1.1')
25.1
Good catch. It does work on latest stable Tahoe though, that's where we tested it.
> parseFloat('25.0.1') 25 > parseFloat('25.1.1') 25.1
Would be great if you guys enabled it in 25.1 since the issue exists in the 25.1 beta as well
Overall it's looking very unlikely that Apple will do anything about this issue, so >= 25 seems reasonable to me
There's a big group of people who opted into 25.1 beta in those exact hopes but were let down, so we're stuck with beta
edit: 1.9.0-pre.2.patch.0 fixes the GPU issue for all Tahoe versions. fantastic!
Sure, will be fixed in next build.
That's unfortunate to hear as I was also hoping Apple would do something here.
I appreciate this issue being addressed! This should be released in the nightly release for October 21st, 2025?
so is this fix shipped in 2.0 stable? and on 26.1 beta?
Cursor 2.0.40 still seems to list Electron 34.5.8, so I'm a little skeptical that this is fixed, unless the Electron version number was not updated? 🤔
Edit: I was misguided - this was not fixed by an Electron version bump but rather a hotfix. See comment: https://github.com/cursor/cursor/issues/3672#issuecomment-3469227711
Cursor 2.0.40 still seems to list Electron 34.5.8, so I'm a little skeptical that this is fixed, unless the Electron version number was not updated? 🤔
![]()
It's fixed via hotfix that's unrelated to electron version. I have confirmed it's fixed
I can say that it still has terrible lag even as they updated Electron, takes 100% of my CPU for the duration of initial 20 seconds.