anomalyco / anomalyco/opencode
Desktop 1.18.30: utility NodeService crashes intermittently on quit (SIGABRT/SIGSEGV)
Open
@Hona is already working on this.
Since Sep 10, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
Environment:
- OpenCode Desktop 1.18.30 (deb, updated from 1.18.25), channel latest
- App running inside Ubuntu 24.04 distrobox container on Fedora Kinoite 44 host
- Native modules in crashing process: @lydell/node-pty-linux-x64 1.2.0-beta.12,
@parcel/watcher-linux-x64-glibc 2.5.1 (verified under
/opt/OpenCode/resources/app.asar.unpacked/node_modules/)
Repro:
- Open OpenCode Desktop, use normally, then quit.
- Repeat open/quit ~4 times. About 1 in 4 quits shows a crash notification
for the utility process. 3 of 4 quits are clean.
Crash data (systemd-coredump):
ai.opencode.desktop --type=utility --utility-sub-type=node.mojom.NodeService
Signal 6 (ABRT) and Signal 11 (SEGV) on different quits, always at quit time.- Core sizes 36-49 MB truncated (host limits: ProcessSizeMax=1G); one 46 KB.
- utility.log at crash second:
[warn] (utility) sidecar exited { code: 0 } - main.log clean, updater reports 1.18.30 up-to-date.
- GDB on host cannot resolve container paths (/opt/OpenCode only exists in
container), core truncated so no symbol stack; file-backed mapping notes
confirm pty.node + watcher.node loaded in the crashing process.
Ruled out:
- Crash reproduces with ALL MCPs disabled (
enabled: falsefor every entry
in opencode.jsonc), so it is not caused by any MCP server. - Reproduced on 1.18.25 and 1.18.30.
Possibly related:
- microsoft/node-pty#904 (SIGABRT during Electron exit, ThreadSafeFunction
cleanup race with node-pty) - opencode#17068 (sidecar not terminated on Desktop close)
Attachments: Crashpad .dmp from
~/.config/ai.opencode.desktop/Crashpad/pending/ + utility.log snippet above.
a7bf82a0-29f0-4a8c-91f4-c4cd85f1d361.zip
Plugins
No response
OpenCode version
1.18.30.
Steps to reproduce
No response
Screenshot and/or share link
No response
Operating System
Ubuntu 24.04 (distrobox container) on Fedora Kinoite 44 host
Terminal
Konsole 26.08
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.