You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 2d46b95
Browse filesBrowse the repository at this point in the historyBrowse files
fix(desktop,web): contain renderer memory growth and recover from renderer crashes
Long sessions OOM the Electron renderer at V8's heap ceiling (~3.7GB),
leaving a dead white window while agents keep running invisibly.
Three containments, no user-visible behavior change:
- Collapse superseded context-window.updated activities in the live
reducer path. Providers stream these continuously and consumers only
read the latest value per turn, but the client retained every row —
thousands per long thread. Mirrors the rule the server already
applies to snapshots (dropStaleContextWindowActivities), including
its malformed-row and per-turn revert semantics.
- Drop the sidebar thread-detail prewarm from 10 to 3. Each prewarmed
row pins a fully hydrated, live-growing thread subscription for as
long as it is visible; cold opens still render instantly from the
cached snapshot.
- Reload the window on render-process-gone (crashed/oom/abnormal-exit),
bounded to 3 attempts per rolling minute so a boot-crash cannot
reload-loop. The backend is unaffected by renderer death, so a reload
fully rehydrates.
Co-Authored-By: Claude Fable 5 <[email protected]>
0 commit comments