anomalyco / anomalyco/opencode
Desktop sidecar repeatedly crashes with V8 out-of-memory, causing local server red and Failed to fetch
@Hona is already working on this.
Since Aug 12, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
Environment
- OpenCode desktop version: 1.18.16
- Windows
- Clash Verge Rev 2.5.2 with TUN enabled
Problem
The desktop app frequently shows Failed to fetch. At the same time, the local server indicator at the top turns red. Opening a new conversation does not help because all conversations share the same local sidecar.
Reproduction
- Start OpenCode desktop.
- Use one or several conversations.
- After several requests or new conversations, the local server indicator turns red.
- Sending a message fails with
Failed to fetch.
Logs
The sidecar repeatedly crashes with:
OOM error in V8: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
Observed at approximately:
- 2026-08-12 13:44
- 2026-08-12 13:57
- 2026-08-12 13:59
- 2026-08-12 14:10
After the sidecar exits, the renderer reports:
TypeError: Failed to fetch
Restarting the entire OpenCode process temporarily recovers the app. Creating a new conversation does not.
Relevant log directory:
%APPDATA%\ai.opencode.desktop\logs
No account credentials, API keys, or subscription URLs are included.
Plugins
No response
OpenCode version
No response
Steps to reproduce
No response
Screenshot and/or share link
No response
Operating System
No response
Terminal
No response
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.