Skip to content

Segfault in embedded Bun 1.3.14 (JSC microtask drain, llint_op_call_ignore_result loop) on Linux x86_64 baseline — opencode 1.18.34 #52773

Closed as not planned

Description

@bsallesp

Crash

Bun-embedded segfault, reported via bun.report:

https://bun.report/1.3.14/Ba10d9b296mwGugogC4664tE+ypR__suwxrCsuwxrCsuwxrCsuwxrCsuwxrCsuwxrCsuwxrCmsvprCi4wtpFusjtpF8s1muF4r338D__msvprCwpthhFA28n5B4/roh7D

Bun v1.3.14 (0d9b296a) on linux x86_64_baseline [StandaloneExecutable]
Segmentation fault at address 0x7B779ABA01FC
`llint_op_call_ignore_result` x7 -> `llint_call_javascript` -> `JSC::Interpreter::executeCallImpl`
via `JSC::MicrotaskQueue::drain` / `JSC::VM::drainMicrotasks` / `Bun::jsFunctionDrainMicrotaskQueue`,
with `JSGenerator` frames on the microtask path (`JSMicrotask.cpp:143`, `MicrotaskCallInlines.h:84`)
Features: spawn, standalone_executable, workers_spawned, napi_module_register, process_dlopen, Bun.stderr, Bun.stdin, Bun.stdout, fetch, jsc

OpenCode version

1.18.34 (npm [email protected], latest tag). Verified the binary embeds Bun 1.3.14 (bun-linux-x64-baseline.zip / v1.3.14 (0d9b296a) strings). Today's dev snapshot (0.0.0-dev-202610020321) still embeds Bun 1.3.14 as well, so no available build fixes this yet.

Environment

  • Linux x86_64 (glibc, AVX2 capable), kernel via Hetzner cloud VM
  • Long-running opencode serve --port 4096 + TUI sessions + a Telegram bot holding SSE streams per directory
  • The serve process survived (uptime 2+ days); the crash took down a client-side process (TUI/one-shot run)

Notes

Activity

  1. github-actions commented on Oct 2, 2026

    @github-actions
    Contributor

    This issue doesn't fully meet our contributing guidelines.

    What needs to be fixed:

    • Please use the Bug Report template and include its required Description field. The report has useful crash details, but currently uses custom Crash, Environment, and Notes headings instead of the template.
    • Please add reproduction steps or, if the trigger is unknown, clarify what action was in progress when the crash occurred. The current report describes the setup but not a specific trigger.

    Please edit this issue to address the above within 72 hours, or it will be automatically closed.


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

    • #40219: Repeated Bun 1.3.14 segfaults on Linux x64 during long-running sessions, with a similar crash-report signature.
    • #38199: Bun 1.3.14 segfault with a similar JSC microtask-drain/generator stack family, though the platform and trigger differ.
    • #40812: Repeated Bun 1.3.14 crashes on Linux x64 while running opencode serve; the reported crash signature differs.

    If you believe this was flagged incorrectly, please let a maintainer know.

  2. github-actions commented on Oct 5, 2026

    @github-actions
    Contributor

    This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 72-hour window.

    Feel free to open a new issue that follows our issue templates.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions