[Bug]: Process crashes with "setRawMode failed with errno: 5 (EIO)" when terminal disconnects #15286

Activity

1. github-actions

   assigned

   rekram1-node

   on Feb 26, 2026
2. github-actions

   added

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   opentuiThis relates to changes in v1.0, now that opencode uses opentuiThis relates to changes in v1.0, now that opencode uses opentui

   on Feb 26, 2026
3. github-actions commented on Feb 26, 2026

   

   github-actionsBot

   on Feb 26, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of or closely related to an existing issue. Please check:

   • Missing SIGHUP handler causes orphaned processes to leak ~4.7 GB each after terminal death #14504: Missing SIGHUP handler causes orphaned processes after terminal death — both issues deal with opencode failing to handle terminal disconnection gracefully, though Missing SIGHUP handler causes orphaned processes to leak ~4.7 GB each after terminal death #14504 focuses on orphaned processes/memory leak while this issue focuses on the EIO crash from setRawMode.
4. papajade55-debug commented on Apr 23, 2026

   

   papajade55-debug

   on Apr 23, 2026

   More actions

   Additional symptom in v1.14.21: opencode.json truncated to 0 bytes on EIO shutdown

   Same setRawMode errno: 5 crash, but with a secondary data-loss side effect — the config file gets wiped to 0 bytes.

   Reproduction (100% reliable on my machine):

   1. Start opencode TUI (v1.14.21, Linux)
   2. Close/exit normally (no terminal crash required)
   3. ls -la ~/.config/opencode/opencode.json → 0 bytes

   Log evidence (consecutive cycles):

   ERROR service=server-proxy e=setRawMode failed with errno: 5 exception
   ERROR service=server-proxy error=setRawMode failed with errno: 5 process error
   INFO  service=server-proxy worker shutting down
   INFO  service=server-proxy disposing all instances
   

   The file mtime matches the shutdown timestamp to the second. Confirmed across two independent test cycles.

   Hypothesis: a shutdown finalizer attempts to serialize the loaded config back to disk after the EIO fault, but writes empty content due to the degraded state.

   Workaround: chmod 444 ~/.config/opencode/opencode.json — the readonly bit prevents the faulty write; plugin loading (path=opencode-tool-search loading plugin confirmed in log) and normal runtime work fine. To edit the file later, chmod 644, modify, then chmod 444 again before relaunch.

   Environment: opencode 1.14.21, Linux Mint 22.3 (Ubuntu 24.04), kernel 6.17.0, Node v24.13.1, GNOME Terminal.

   This suggests the fix for this issue should not only handle EIO gracefully but also ensure the config-save path is guarded against writing empty/partial state during abnormal shutdown.
5. thdxr

   closed this as completedon Apr 27, 2026
6. juleslemee commented on May 26, 2026

   

   juleslemee

   on May 26, 2026

   More actions

   @thdxr had the same exact log signature from a crash yesterday on 1.15.10. Opus 4.7 : "looking at your log, you have worker shutting down between the EIO errors, which the original reporter didn't. That suggests opencode now attempts graceful shutdown on EIO instead of crashing hard, but it still has to exit (terminal's gone). The fix addressed the symptom (no graceful shutdown), not the underlying TTY-state issue that triggers EIO in the first place. Long-lived sessions and any TTY disturbance (display sleep, terminal app backgrounded, window close) will still hit it."