TUI crashes during prompt edit #3749

Activity

1. tsukinoko-kun

   added

   bugSomething isn't workingSomething isn't working

   on Nov 2, 2025
2. github-actions

   added

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

   on Nov 2, 2025
3. tsukinoko-kun commented on Nov 2, 2025

   

   tsukinoko-kun

   on Nov 2, 2025

   Author

   More actions

   It's sad seeing this app crumble. It was the best agentic editor for a while.

   👍React with 👍1Reacted by leobar

   😕React with 😕1Reacted by Scott Baxter
4. github-actions commented on Nov 2, 2025

   

   github-actionsBot

   on Nov 2, 2025 – with GitHub Actions

   Contributor

   More actions

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

   • Opencode is able to crash the terminal #3691: Terminal/shell crashes - similar TUI crash behavior that affects the terminal
   • Edit Mode is not exiting properly #3648: Screen redraw issues after editing - similar editing-related TUI display problems
   • Enter (send) does not work after cmd+opt+k #3745: Command+Option keyboard shortcut issues on macOS - similar macOS keyboard shortcut problems

   Feel free to ignore if none of these address your specific case.
5. veracioux commented on Nov 2, 2025

   

   veracioux

   on Nov 2, 2025

   Contributor

   More actions

   To the maintainers: I did some experimentation, and while I couldn't replicate the SIGTRAP, I do get a SIGABRT, with this printed:

   /usr/include/c++/13/array:202: reference std::array<unsigned long, 16>::operator[](size_type) [_Tp = unsigned long, _Nm = 16]: Assertion '__n < this->size()' failed.
   

   (maybe more is printed which I'm not able to see because of the already-rendered TUI)

   My specs: Arch Linux, Alacritty

   Reproducing

   1. Paste a long text into the prompt textarea
   2. Hold alt+backspace or regular backspace

   It is kinda unpredictable after how much time it will crash, but I am able to reproduce quite consistently. alt+backspace seems more likely to reproduce it than plain backspace. Also might depend on the keyboard repeat rate - I have mine set to quite high.

   @kommander This seems to be an opentui issue because I reproduced with a minimalistic opentui project:

   https://gist.github.com/veracioux/167b3645c23ccb29620814789ea1565f

   In this project, sometimes it crashes with SIGABRT and an error message as the one above, and sometimes with this one:

   Bun v1.3.1 (89fa0f34) Linux x64                                                                                     │
   Linux Kernel v6.17.1 | glibc v2.42                                                                                  │
   CPU: sse42 popcnt avx avx2 avx512───────────────────────────────────────────────────────────────────────────────────┘
   Args: "bun" "src/index.ts"
   Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) bunfig fetch jsc transpiler_cache tsconfig(2) tsconfig_paths(2) virtual_modules(2)
   Builtins: "bun:ffi" "bun:main" "node:assert" "node:buffer" "node:console" "node:events" "node:fs" "node:fs/promises" "node:module" "node:os" "node:path" "node:stream" "node:tty" "node:url" "node:util"
   Elapsed: 716ms | User: 343ms | Sys: 89ms
   RSS: 1.10GB | Peak: 0.14GB | Commit: 1.10GB | Faults: 1 | Machine: 29.21GB
   
   panic(main thread): Segmentation fault at address 0x7F90872C29A0
   oh no: Bun has crashed. This indicates a bug in Bun, not your code.
   

   👍React with 👍1Reacted by Sebastian
6. Regboy744 commented on Nov 2, 2025

   

   Regboy744

   on Nov 2, 2025

   More actions

   Bug Report: Segmentation Fault on Bun v1.3.0

   Description
   Bun crashes with a segmentation fault (address 0x783C21E1E220) immediately upon startup. The crash appears to occur during the initialization phase.
   What happened:

   Bun terminated with "Segmentation fault at address 0x783C21E1E220"
   The process crashed before executing any user code
   No specific error message about what caused the crash

   

   Bun version: v1.3.0 (b0a6faca)
   OS: Linux x64 (baseline)
   Kernel: Linux v6.12.56
   glibc: v2.42
   CPU: sse42 popent avx avx2 avx512

   
   ### **When** it happens:
   The crash occurs immediately when running Bun, during the startup/initialization phase.
   
   ### **Error Output**
   

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

   
   ### **System Information**
   - **RAM**: 1.016B
   - **Peak Memory**: 0.27GB
   - **Commit**: 1.016B
   - **Faults**: 0
   - **Machine**: 41.756B
   
   ### **How to Reproduce**
   1. Install Bun v1.3.0
   2. Run any Bun command (even `bun --version`)
   3. Observe segmentation fault
   
   ### **Expected Behavior**
   Bun should start normally without crashing.
   
   ### **Actual Behavior**
   Bun crashes with a segmentation fault before executing any code.
   
   ### **Additional Context**
   - The crash report shows multiple Node.js compatibility modules being loaded
   - Error occurs at memory address: `0x783C21E1E220`
   - Elapsed time before crash: 6298ms
   - User: 1436ms | Sys: 301ms
   
   ### **Possible Related Information**
   The crash log shows various Node.js built-in modules being loaded:
   - `node:assert`, `node:async_hooks`, `node:buffer`, `node:child_process`, `node:console`, `node:crypto`, `node:events`, `node:fs`, `node:http`, `node:https`, `node:module`, `node:net`, `node:os`, `node:path`, `node:process`, `node:readline`, `node:stream`, `node:string_decoder`, `node:timers`, `node:timers/promises`, `node:tls`, `node:tty`, `node:url`, `node:util`, `undici`
   
7. kommander commented on Nov 2, 2025

   

   kommander

   on Nov 2, 2025

   Contributor

   More actions

   @veracioux from opentui the only thing that is c++ would be yoga-layout. Would need to run this with lldb and a debug build of bun and opentui.
8. kommander

   self-assigned this

   on Nov 4, 2025
9. thdxr

   closed this as completedon Mar 25, 2026