Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dragging/maximizing the console wallet on windows causes it to crash #6729

Open
stringhandler opened this issue Dec 30, 2024 · 3 comments
Open
Assignees

Comments

@stringhandler
Copy link
Collaborator

stringhandler commented Dec 30, 2024

To reproduce:

Open console wallet on windows.

Maximize it, then drag it to a new location.

Expected: maximizing and dragging works.

Actual: console wallet closes, I assume a panic.

NOTE: seems to happen on the second or third resize that happens

@hansieodendaal
Copy link
Contributor

Performing a high level investigation showed that different results are obtained when using Windows Console Host or Windows Termimal as the default terminal application, or wether Windows 10 or Windows 11 are used.

tldr; For the current Console Wallet application, running on Windows 10 and using Windows Console Host is a bad combination.

Image

  • Using Windows Console Host as the defaiult terminal application:
    • Windows 10 (22H2)
      • Console Wallet crashes on the first maximize - drag or maximize - reset attempt
    • Windows 11 (24H2)
      • Console Wallet never crashes on any first maximize - drag or maximize - reset attempt
  • Using Windows Terminal as the defaiult terminal application:
    • Windows 10 (22H2)
      • Console Wallet never crashes on any first maximize - drag or maximize - reset attempt
    • Windows 11 (24H2)
      • Console Wallet never crashes on any first maximize - drag or maximize - reset attempt

@hansieodendaal
Copy link
Contributor

Error details with Windows 10

2025-01-20 11:07:32.673156500 [wallet::app::crossterm_events] ERROR Internal error in crossterm events: No process is on the other end of the pipe. (os error 233)
2025-01-20 11:07:32.673416100 [wallet::app::crossterm_events] ERROR Internal error in crossterm events: No process is on the other end of the pipe. (os error 233)
2025-01-20 11:07:32.673449300 [wallet::app::crossterm_events] ERROR Internal error in crossterm events: No process is on the other end of the pipe. (os error 233)
2025-01-20 11:07:32.673469100 [wallet::ui::app] ERROR Error drawing interface. No process is on the other end of the pipe. (os error 233)
2025-01-20 11:07:32.673488200 [wallet::app::crossterm_events] ERROR Internal error in crossterm events: No process is on the other end of the pipe. (os error 233)

...

2025-01-20 11:07:32.923368000 [wallet::app::crossterm_events] ERROR Internal error in crossterm events: No process is on the other end of the pipe. (os error 233)
2025-01-20 11:07:32.923380000 [wallet::app::crossterm_events] ERROR Internal error in crossterm events: No process is on the other end of the pipe. (os error 233)
2025-01-20 11:07:32.923387800 [wallet::app::crossterm_events] INFO  Tick event channel shutting down

@hansieodendaal
Copy link
Contributor

This test PR contains test code and some results: hansieodendaal#17

tldr; The backend crossterm process dies with maximize -> reset. This also holds for the latest release crossterm = { version = "0.28.1" }

@hansieodendaal hansieodendaal self-assigned this Jan 20, 2025
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

No branches or pull requests

2 participants