1 person reported

All time, since Sep 16.

Glass renderer runs out of memory

“One glass window, left up with local agent loops, died twice in the same day.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/cursor/issues/2474/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Glass renderer runs out of memory as text models leak. Long-running glass window with local agent loops hits the 4096 MB heap cap; ModelService._createModelData listeners never released.

Is this your bug?

File my report
Where
Glass window renderer
Error text
CodeWindow: renderer process gone (reason: crashed, code: 132)
Versions
3.20.17
Platforms
Linux
How bad
Stops work: a core feature can't be used.

Original reports2, newest first

  1. Glass renderer OOM: hidden diffs, Review Changes, and agent transcripts never leave memory#172039
  2. Glass renderer OOM: text models / working copies never released#171837

Do you work on Cursor?

Claim its RAP Sheet to see what your users report and answer them in one place.