Skip to content

opencode crashes over and over #9599

Closed
Closed

Description

@zoonosis

UPDATE: so i built it from source via git and used bun 1.3.6 and it still crashes

Bun v1.3.6 (d530ed9) on windows x86_64 [AutoCommand]

Segmentation fault at address 0x5C22E1E0100

Features: spawn, standalone_executable, transpiler_cache, tsconfig, tsconfig_paths, workers_spawned, napi_module_register, process_dlopen, Bun.stderr, Bun.stdin, Bun.stdout, abort_signal, dotenv, fetch, http_server, jsc, shell, shell

If this a bug in bun, then how do we force the upgrade or downgrade of the bundled bun that comes inside opencode???

Description

just using base vanilla opencode and no matter what I do it crashes continuously. ive removed every plugin. tried just cli, vscode, no vsocde, powershell, nothing works. its unusable.

Bun v1.3.5 (1e86cebd) Windows x64 (baseline)
Windows v.win10_cux M2.1 OpenCode Zen
CPU: sse42 avx avx2▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Args: "\AppData\Roaming\npm\node_modules\opencode-ai\node_modules\opencode-windows-x64\bin\opencode.exe" "--user-agent=opencode/1.1.26" "--use-system-ca " "--" "-c" tab agents ctrl+p commands
Features: Bun.stderr(4) Bun.stdin(4) Bun.stdout(4) abort_signal(2) dotenv(2) fetch(6) jsc shell(34) spawn(29) standalone_executable transpiler_cache tsconfig workers_spawned(2) napi_module_register process_dlopen
Builtins: "bun:ffi" "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:console" "node:crypto" "node:dns" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:process" "node:querystring" "node:readline" "node:stream" "node:string_decoder" "node:timers" "node:timers/promises" "node:tls" "node:tty" "node:url" "node:util" "node:worker_threads" "undici" "node:v8" "node:http2" "node:diagnostics_channel" "node:dgram"
Elapsed: 57407ms | User: 4984ms | Sys: 578ms
RSS: 0.78GB | Peak: 0.93GB | Commit: 1.00GB | Faults: 302009 | Machine: 17.09GB

panic(thread 16668): Segmentation fault at address 0x32F1F372C20
oh no: Bun has crashed. This indicates a bug in Bun, not your code.

To send a redacted crash report to Bun's team,
please file a GitHub issue using the link below:

Bun v1.3.5 (1e86ceb) on windows x86_64_baseline [AutoCommand]

Segmentation fault at address 0x21E42971020

Features: spawn, standalone_executable, transpiler_cache, workers_spawned, napi_module_register, process_dlopen, Bun.stderr, Bun.stdin, Bun.stdout, abort_signal, fetch, http_server, jsc, shell, shell

Plugins

none

OpenCode version

1.1.26

Steps to reproduce

just use it normally and itll crash, seriously. happens every few minutes. ram gets chewed up and boom.

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Activity

  1. github-actions commented on Jan 20, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    All of these report similar Bun segmentation faults on Windows with continuous crashes and memory issues. These might be related to the same underlying Bun issue on Windows.

    Feel free to ignore if your specific case differs from these.

  2. Aaalice233 commented on Jan 20, 2026

    @Aaalice233

    same

  3. zoonosis commented on Jan 20, 2026

    @zoonosis
    Author

    i built it from source using the latest bun and it still crashes

    git clone https://github.com/anomalyco/opencode.git
    cd opencode
    bun install

  4. rekram1-node commented on Jan 20, 2026

    @rekram1-node
    Collaborator

    oh no: Bun has crashed. This indicates a bug in Bun, not your code.

    Yeah these crashes come from Bun itself, if you don't mind opening issues in Bun :)

  5. zoonosis commented on Jan 21, 2026

    @zoonosis
    Author

    @rekram1-node I send it to them via the automated crash link that pops up when it crashes. ive also logged it with them on their github. Is there anything I can do in the meantime to stop this? i can only work for like 2 minutes before it falls over. Do I have to use linux or something in the meantime?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingperfIndicates a performance issue or need for optimizationwindows

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions