Repository navigation
Bun panic (Illegal instruction) + severe memory leak after ~12h session — opencode 1.17.14 on Windows 11 #35847
Closed as not planned
Description
Description
opencode 1.17.14 crashes after long-running sessions (~12 hours) with a Bun runtime panic (Illegal instruction), accompanied by severe memory growth. RSS reached 42.90 GB (peak 45.29 GB) and system memory usage hit 94% (59.8 / 63.4 GB) right before the crash.
The crash output explicitly states: "Bun has crashed. This indicates a bug in Bun, not your code."
Crash details (from terminal)
Bun v1.3.14 (0d9b296a) Windows x64 (baseline)
Windows v.win11.dt · glm-5.2 huoshan3
CPU: sse42 avx avx2
Args: "D:\software\program\nvm\nvmw\nodejs\node_modules\opencode-ai\bin\opencode.exe" "--user-agent=opencode/1.17.14" "--use-system-ca" "--" "--port" "35743"
Elapsed: 44071920ms | User: 14254046ms | Sys: 2566156ms
RSS: 42.90GB | Peak: 45.29GB | Commit: 52.30GB | Faults: 398193872 | Machine: 68.08GB
panic(main thread): Illegal instruction at address 0x7FF6E198A852
oh no: Bun has crashed. This indicates a bug in Bun, not your code.
Memory state (Task Manager at crash time)
| Metric | Value |
|---|---|
| Memory | 59.8 / 63.4 GB (94%) |
| In use (compressed) | 59.8 GB (811 MB) |
| Available | 3.6 GB |
| Committed | 98.8 / 100.0 GB |
| Cached | 3.6 GB |
| Non-paged pool | 1.6 GB |
| Page faults | 398,193,872 |
Crash report
Bun generated a redacted crash report:
https://bun.report/1.3.14/ea10d9b296mWG+gooCkl0u+CoqkvtDq1+koDg9lz+Ciumz+C+6g+uC6l97uC6o87uC8967uC6ook4B4u/j4BstsJ4Bs13s2Bwzxs2B___A3s//B96r9se
OpenCode version
1.17.14
Steps to reproduce
- Launch opencode 1.17.14 on Windows 11 (Bun v1.3.14 baseline).
- Keep a session running for an extended period (~12 hours in this case).
- Observe memory usage growing continuously (RSS climbed to ~43 GB).
- Eventually the process panics with
Illegal instructionand crashes.
Screenshot and/or share link
Two screenshots attached below:
- Screenshot 1: terminal crash output (Bun panic + full diagnostics)
- Screenshot 2: Task Manager showing 94% memory usage at crash time
Operating System
Windows 11
Terminal
Windows Terminal
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Jul 8, 2026
This issue might be a duplicate of existing issues. Please check:
opencode serveaccumulates anonymous JS heap/swap with 26.8 GiB peak — very similar unbounded memory growth profileIf your issue is already covered by one of the above, please add a comment there with your diagnostics rather than opening a new report. If it is distinct (e.g., the
Illegal instructionpanic at a specific address is the primary issue rather than just OOM), please clarify what differs so maintainers can triage it separately.touful commentedon Jul 8, 2026
The user @guvubededome who posted that attachment:
This is a classic supply-chain phishing pattern: a throwaway account monitoring new issues and dropping a "fix" attachment that is almost certainly malicious malware.
Do not download, extract, or run
opencode_fix.zip. I have reported the account to GitHub for abuse. Legitimate fixes will always come through a PR reviewed by maintainers, never a zip attachment from a brand-new account in an issue comment.If you already downloaded/ran it, treat your machine as compromised: disconnect from network, run a full AV scan, rotate credentials that may have been on that machine.
touful commentedon Jul 8, 2026
Cross-referencing related issues for maintainer triage:
The
github-actionsbot flagged several related issues. After reviewing them, here's how this one maps:structuredClone+ mimalloc not returning pages)Illegal instructionat0x7FF6E198A852(not segfault/SIGSEGV) — a distinct crash signature that may point to a different code path (possibly AVX2 JIT, given the CPU flagsavx avx2)Suggestion for maintainers:
Illegal instructionpanic at a specific address is a distinct crash signature from the segfault in OpenCode v1.17.10 crashes with Bun segmentation fault on Windows; v1.17.9 appears stable #33742. If the maintainers consider them the same underlying bug, this can be folded in; if not, it may warrant separate triage sinceIllegal instruction(typically JIT/AVX2 related) can have a different root cause thanSIGSEGV.A full redacted Bun crash report is available at:
https://bun.report/1.3.14/ea10d9b296mWG+gooCkl0u+CoqkvtDq1+koDg9lz+Ciumz+C+6g+uC6l97uC6o87uC8967uC6ook4B4u/j4BstsJ4Bs13s2Bwzxs2B___A3s//B96r9seTwo screenshots (terminal crash output + Task Manager at 94% RAM) will be attached shortly.
2015chunhui commentedon Aug 27, 2026
我也是， 长时间运行后， 就直接内存 crash 了；有没有临时规避的方法
thdxr commentedon Oct 11, 2026
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (
opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊