Repository navigation
[Desktop field report] 34.59 GB app-group memory and low-memory force quit after an 8.5 h session with 5 subagents #10837
xiaodianshiuwu
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.
Summary
DSH Desktop
0.2.1-rc.2on macOS 26.7.1 / 16 GB Apple Silicon reached an app-group memory value of 34.59 GB after one long-lived session (8 h 34 min) that included 5 subagent sessions and substantial tool output/screenshot activity. macOS showed the low-memory panel and the renderer was killed; the app was then force-quit. The same panel showedPythonat 34.59 GB, which appears to be the same app group / child process counted at group level, not a second independent 34 GB process.This is a field report, not a deterministic 5-minute reproduction. I do not have a retained heap snapshot; I am reporting the process timeline, session scale and logs so the desktop/renderer and session-retention paths can be investigated together.
Environment
0.2.1-rc.244.7.0, bundled Node24.21.0dsh-better-sidebarinstalled; itssidebar/ws/agent-opensreconnect loop logged failures for the subagent sessionsTimeline (local time)
At the low-memory dialog, the old DSH app group showed 34.59 GB.
Pythonalso showed 34.59 GB. No independent Python process of that size remained after the app group exited; the current Python bridge is ~25 MB.Session scale
Current behavior
dsh-better-sidebarlogged repeatedagent-opens connection failed; stopping reconnect loopfor the subagent sessions; this may be secondary, but it is part of the same session-switching workload.Expected behavior
Related reports
Request
Please treat this as desktop evidence for the same memory-budget problem: 8.5 h session + 5 subagents + large tool output on a 16 GB Mac produced a 34.59 GB app-group value and a low-memory force quit. I can provide additional sanitized logs or a session-size fixture if useful; I will not upload account data, local paths, session IDs or screenshots containing personal information.
Sanitization
All local usernames, home paths, account identifiers, session IDs, thread IDs and credentials have been removed. Process IDs are omitted or shown as
<old-pid>.All reactions