Repository navigation
Desktop renderer memory grows with cumulative session history, causing progressive lag and repeated OOM crashes #12672
wangyouhanh
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Environment
Describe the bug
The desktop renderer memory scales with the cumulative size of a session history, not with current activity. With one long-running session (many turns, large tool outputs, code blocks), the following cycle repeats:
ResizeObserver loop completed with undelivered notificationsbefore crashes.Expected behavior
Renderer memory should stay bounded regardless of total session length: virtualized/windowed rendering of the message list, lazy loading of older events, UI-side truncation of very large tool outputs, or a per-session memory budget. Displaying a long conversation should not require gigabytes of RAM.
Suspected cause
The web UI appears to eagerly load and render the full session event history. Heap and DOM size grow linearly with cumulative event count, causing frequent GC pauses (the lag) and eventually an OOM kill of the renderer.
Reproduction outline
Additional notes
Related discussions (searched before posting; this report adds independent reproduction measurements, cross-linked to keep reports connected):
All reactions