Repository navigation
Replies: 1 comment
|
中文摘要(给维护者速读)
|
0 replies
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 on Windows x64 aborts the host child process with a V8 heap OOM (
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory), exit code 134. The shell then reportsdsh desktop host exited with 134and shows the "应用无法启动或意外停止" dialog. Sessions are preserved and the app can restart, but the interruption is recurring and predictable by uptime.Two occurrences on the same machine, same signature:
The second occurrence happened after the profile had been reset to first-party-only configuration (no third-party plugins / MCP inserts in
cordis.patch.yml), so this does not appear to require third-party plugins to reproduce.Environment
@deepseek-ai/dsh-desktop)ui-settings-account/ui-chat/ui-settingsconfig)%APPDATA%\@deepseek-ai\dsh-desktop(data),~/.dsh(session store)Current behavior
Both crash logs (
crash-*-host.log) end with the same sequence:and the shell-side error is:
The host heap effectively caps out around ~3.15 GB before the abort, which suggests the host is being started with a ~3 GB
--max-old-space-size(or similar) budget.Relevant session store size on this machine (for the leak / retention hypothesis):
~/.dsh/sessions: 215 files, ~799 MB compressed in totalsession.v4.jsonl.zstdsegments up to 2.7 MBExpected behavior
heap out of memoryas a recoverable condition (restart host, keep session, tell the user) rather than an opaque native abort.Hypotheses / related reports
This looks like the same memory-budget family as existing reports, but with a distinct Windows host-process V8 OOM signature:
My case differs in that the host survives startup and dies only after many hours, while the crash log shows a slow growth to the ~3.15 GB heap ceiling. So it may be (a) a genuine leak in host-side session/projection retention, (b) the per-session in-memory log never being trimmed (see #4722), or (c) a fixed ~3 GB heap cap that long sessions inevitably reach.
Request
--max-old-space-sizefor the host).Sanitization
User name and home paths are redacted (
C:\Users\<user>). No tokens, account data, session IDs, or message content are included.Workaround in use
Restart the desktop app once per day, and restart when the host process exceeds ~2 GB RSS. This roughly doubles the safe interval but does not fix the growth.
All reactions