Skip to content

Conversation

@Arthur742Ramos
Copy link
Contributor

Fixes #10414

Summary

  • Adds SIGINT handler in App component to properly cleanup renderer on Ctrl+C
  • Prevents 60 FPS render loop from continuing to output ANSI sequences after exit

Verification

  1. Ran bun dev on Windows
  2. Pressed Ctrl+C
  3. Terminal exited cleanly without garbled escape sequence output

Fixes anomalyco#10414

On Windows, pressing Ctrl+C caused the terminal to output ANSI escape sequences because the 60 FPS renderer was not being properly cleaned up. This adds a SIGINT handler in the App component that calls the exit function to properly destroy the renderer.
@github-actions
Copy link
Contributor

The following comment was made by an LLM, it may be inaccurate:

Potential Related PR Found:

@Arthur742Ramos
Copy link
Contributor Author

The test failures are pre-existing issues on the dev branch (e2e tests in packages/app are failing). This PR only modifies TUI code in packages/opencode/src/cli/cmd/tui/app.tsx which is not covered by those e2e tests. The typecheck workflow passes.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

OpenCode crashes during use on Windows (garbled console output)

1 participant