Cursor is responsible of 99% of my OOM errors of my system. Agents tab consumes less memory than IDE but still causes OOM errors all the time. I believe every UI integration isnt properly UI updated with a lot of bottlenecks and lots of data in memory that could have been cleared
Hey @anoncoder555, thanks for the report, and sorry about the OOM trouble.
One thing to check first: the Cursor installation we see reporting from your machine is on version 3.9.16 (a build from late June), not 3.20. Could you open Cursor → Help → About and confirm the version? On Linux, .deb and .rpm installs do not update themselves, so it is easy to end up on an old build without noticing.
A lot of memory work has shipped since 3.9, especially for the Agents window, so please update to the current release first: grab the latest from Cursor · Download (the AppImage keeps itself up to date; for .rpm/.deb you need to install the new package or use our apt/yum repository). Then use it for a day or two the way you normally would.
If it still runs out of memory on the new version, this would help us pin it down:
When memory starts climbing, open Help → Open Process Explorer and tell us which process is the big one (renderer, extension host, or something the agent launched like a build or dev server).
In the Agents window, open the command palette (Ctrl+Shift+P), run “Capture and Send Debugging Data”, tick “Renderer heap snapshot” (leave the defaults ticked), and press Enter. Please do this while the Agents window is around 1.5 to 2.5 GB, not after it has already stalled.
Let me know how this goes and if you see any improvements after updating. Also let me know if you have any trouble updating as I can walk you thru the steps for how to do so on Linux.
