anomalyco / anomalyco/opencode
SIGILL crash after screen unlock — mouse coordinates written to terminal
@simonklee is already working on this.
Since Sep 14, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
opencode crashes with SIGILL after the screen wakes from lock. It works fine at startup but fails after being idle. Before crashing, moving the mouse over the opencode window causes cursor coordinates to be printed to the terminal — looks like mouse escape sequences are getting through and corrupting the buffer.
Running inside tmux with mouse on, foot terminal, Hyprland.
Version: 1.18.30
OS: Omarchy 4.0.3 (Arch Linux), kernel 7.2.3, AMD Ryzen 7 7800X3D
Terminal: foot, inside tmux (mouse enabled)
Steps to reproduce:
- Run
opencode --autoinside tmux (mouse on) inside foot terminal - Leave idle until screen lock activates (~5 min)
- Unlock screen and resume
- Crash with SIGILL
No crash on fresh start, only after wake from lock.
Technical detail: The crash is at offset 0x2407064 which contains a ud2 instruction (unreachable-code assertion) inside napi_acquire_threadsafe_function. Similar to #38986 but our CPU has AVX-512, and the trigger is screen unlock + mouse events rather than startup.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.