Client crashes with SIGABRT on stderr write when host terminal is closed

[abuamar142]

Current behavior

Closing the host terminal (Ghostty) without detaching first (Ctrl+B Q) causes the herdr client to crash with SIGABRT. A core dump is generated. The crash occurs when the client attempts to write to stderr after the terminal's file descriptors have become invalid.

Expected behavior

The herdr client should handle terminal death gracefully — clean disconnect and exit cleanly (exit 0 or exit 1) instead of panicking/aborting. For comparison, tmux handles this scenario without crashing.

Reproduction

1. Open herdr in a terminal (herdr)
2. Open a few panes/tabs
3. Close the terminal window directly (do not detach with Ctrl+B Q first)
4. Core dump is generated

Impact

Core dump occurs every time the terminal is closed without detaching. This is a common mistake, especially when closing multiple windows quickly. The core dump fills systemd journal and coredumpctl with crash reports.

Environment

• herdr v0.8.0 stable
• OS: CachyOS (Arch-based), Linux
• Terminal: Ghostty 1.3.1
• Shell: Fish 4.8.1
• Session: Wayland

Additional context

The crash stack trace shows the abort happens in std::io::default_write_fmt → Stderr::write_str — the client panics when trying to write to stderr after the terminal FD is closed.

[akbash-bot]

Thanks — this is the same v0.8.0 terminal-hangup abort tracked in #2424. The fix is in #2427, with the remaining remote-client shutdown path fixed in #2827; it is available on the preview channel and queued for the next stable release, so I’m consolidating this report there. If this still reproduces on a build containing those fixes, please reply with that exact version and tag @ogulcancelik so we can revisit.

[abuamar142]

Thank you for the quick response and for pointing me to #2427! I'll update once the fix lands in a stable release.