Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Cursor’s renderer falls significantly behind VS Code at 3440×1440, shows no benefit from the experimental GPU-acceleration flag.
60 Hz / 3440×1440
Cursor: ~54 fps average, drops to ~45 fps on tab switch — visibly below the 60 fps target and clearly stuttery.
VS Code: holds 55-60 fps under identical conditions.
180 Hz / 3440×1440
Cursor: tab-switch dips lower to ~48 fps.
VS Code: staying around 90 fps during tab switches.
60 Hz / 1920×1080
Cursor: immediately stable above 55 fps, proving the choke is per-pixel cost at high resolution, not document complexity or AI features.
BTW: Enabling “experimental GPU acceleration” in either editor produces no measurable gain; hardware is Intel UHD Graphics 730.
Steps to Reproduce
- Set monitor refresh rate to the target resolution & frequency (60 Hz or 180 Hz @ 3440×1440; 60 Hz @ 1920×1080).
- In Cursor / VS Code open Developer Tools → Rendering → Frame Rendering Stats.
- Open the same 500-line file, maximise the window, then record average fps while typing and switching tabs for ~30 s.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.7.46 (system setup)
VSCode Version: 1.99.3
Commit: b9e5948c1ad20443a5cecba6b84a3c9b99d62580
Date: 2025-10-14T01:21:46.830Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045
Does this stop you from using Cursor
Yes - Cursor is unusable