Terminal crashes when opening a split-window in settings menu. #22029

Closed
opened 2026-01-31 08:01:28 +00:00 by claunia · 4 comments
Owner

Originally created by @ghost on GitHub (Jul 30, 2024).

Duplicate of #13528
Currently not resolved

Windows Terminal version

1.20.11781.0

Windows build number

10.0.22631.0

Other Software

No response

Steps to reproduce

Start the program
[<ctrl> + T] - Open the settings
[<alt> + <shift> + (+/-)] - Press either the horizontal or vertical split hotkey

Expected Behavior

Eighter the window should

  • not split
  • split into the default terminal emulator specifiend in the configuration.

Actual Behavior

The terminal will stop responding, and eventually crash or just not respond anymore.

Originally created by @ghost on GitHub (Jul 30, 2024). Duplicate of [#13528](https://github.com/microsoft/terminal/issues/13528) Currently not resolved ### Windows Terminal version 1.20.11781.0 ### Windows build number 10.0.22631.0 ### Other Software _No response_ ### Steps to reproduce > Start the program > `[<ctrl> + T]` - Open the settings > `[<alt> + <shift> + (+/-)]` - Press either the horizontal or vertical split hotkey ### Expected Behavior Eighter the window should - not split - split into the default terminal emulator specifiend in the configuration. ### Actual Behavior The terminal will stop responding, and eventually crash or just not respond anymore.
Author
Owner

@similar-issues-ai[bot] commented on GitHub (Jul 30, 2024):

We've found some similar issues:

  • #13528 , similarity score: 82%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@similar-issues-ai[bot] commented on GitHub (Jul 30, 2024): We've found some similar issues: - #13528 , similarity score: 82% If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue. > Note: You can give me feedback by 👍 or 👎 this comment.
Author
Owner

@DHowett commented on GitHub (Jul 30, 2024):

Thanks for filing!

@DHowett commented on GitHub (Jul 30, 2024): Thanks for filing!
Author
Owner

@zadjii-msft commented on GitHub (Aug 21, 2024):

I can't repro this on main (~ 7b39d2491). I also can't repro this on 1.21.1772.0 (Terminal Preview).

I'm guessing this got solved some time in 1.21/?

@zadjii-msft commented on GitHub (Aug 21, 2024): I can't repro this on `main` (~ 7b39d2491). I also can't repro this on 1.21.1772.0 (Terminal Preview). I'm guessing this got solved some time in 1.21/?
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Aug 25, 2024):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service[bot] commented on GitHub (Aug 25, 2024): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**. <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22029