starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Terminal crashes after splitting panes - all profiles, orientations affected #19960

New Issue
Closed
opened 2026-01-31 06:58:43 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 06:58:43 +00:00
Owner
Copy Link

Originally created by @killshot13 on GitHub (May 25, 2023).

Windows Terminal version

1.18.1421.0

Windows build number

10.0.22624.0

Other Software

PowerShell 7.3.4
WSL2: 1.2.5.0
Ubuntu 22.04 LTS
Git for Windows v2.40.1

These are the underlying profiles from which I am attempting to generate the split-pane view.

Steps to reproduce

Easiest Steps:

  1. Open a Windows Terminal Preview tab.
  2. Right-click the tab and select Split Pane from the menu.
  3. Attempt to interact with the terminal or simply wait a few seconds, and it crashes.

Alternative Steps:

  1. Open a Windows Terminal Preview tab.
  2. Use the CTRL-SHIFT-P shortcut to focus the command menu dropdown.
  3. Type Split into the search to populate the relevant commands.
  4. Navigate to the Split Pane option and hit the Enter key.
  5. Attempt to interact with the terminal or simply wait a few seconds, and it crashes.

Expected Behavior

I expected to successfully create multiple panes within the terminal view, and for them to be swappable, movable, and able to be reoriented without affecting the performance of the interface or the shell.

Actual Behavior

I'm not entirely sure my if bug is the same as referenced in #14254 or #14247. But it's extremely similar. However this issue is distinctively broader, because it occurs regardless of which profile is being split and in what orientation. I've attached a short video so you can take a look, and the link to the Feedback Hub submission is down below. 👇

https://github.com/microsoft/terminal/assets/47695475/d980f7fc-600e-445f-8b8c-1625cab41d93

Feedback Hub submission link

Originally created by @killshot13 on GitHub (May 25, 2023). ### Windows Terminal version 1.18.1421.0 ### Windows build number 10.0.22624.0 ### Other Software **PowerShell** 7.3.4 **WSL2**: 1.2.5.0 **Ubuntu** 22.04 LTS **Git for Windows** v2.40.1 _These are the underlying profiles from which I am attempting to generate the split-pane view._ ### Steps to reproduce **Easiest Steps:** 1. Open a Windows Terminal Preview tab. 2. Right-click the tab and select `Split Pane` from the menu. 3. Attempt to interact with the terminal or simply wait a few seconds, and it crashes. **Alternative Steps:** 1. Open a Windows Terminal Preview tab. 2. Use the `CTRL`-`SHIFT`-`P` shortcut to focus the command menu dropdown. 3. Type `Split` into the search to populate the relevant commands. 4. Navigate to the `Split Pane` option and hit the `Enter` key. 5. Attempt to interact with the terminal or simply wait a few seconds, and it crashes. ### Expected Behavior I expected to successfully [create multiple panes](https://learn.microsoft.com/en-us/windows/terminal/panes#creating-a-new-pane) within the terminal view, and for them to be swappable, movable, and able to be reoriented without affecting the performance of the interface or the shell. ### Actual Behavior I'm not entirely sure my if bug is the same as referenced in #14254 or #14247. But it's extremely similar. However this issue is distinctively broader, because it occurs regardless of which profile is being split and in what orientation. I've attached a short video so you can take a look, and the link to the Feedback Hub submission is down below. 👇 --- https://github.com/microsoft/terminal/assets/47695475/d980f7fc-600e-445f-8b8c-1625cab41d93 --- [Feedback Hub submission link](https://aka.ms/AAkxzib)
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 06:58:43 +00:00
claunia commented 2026-01-31 06:58:45 +00:00
Author
Owner
Copy Link

@sephiroth-j commented on GitHub (May 25, 2023):

It happens also when you start a new instance of Windows Terminal Preview (e.g. from the context menu).

grafik

But the Windows Terminal Preview window stays open and is fully usable after closing the Windows dialog. An application error event is logged with the following data.

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
	<System>
		<Provider Name="Application Error"/>
		<EventID Qualifiers="0">1000</EventID>
		<Version>0</Version>
		<Level>2</Level>
		<Task>100</Task>
		<Opcode>0</Opcode>
		<Keywords>0x80000000000000</Keywords>
		<TimeCreated SystemTime="2023-05-25T13:37:22.9375479Z"/>
		<EventRecordID>79999</EventRecordID>
		<Correlation/>
		<Execution ProcessID="0" ThreadID="0"/>
		<Channel>Application</Channel>
		<Computer>XXXX</Computer>
		<Security/>
	</System>
	<EventData>
		<Data>WindowsTerminal.exe</Data>
		<Data>1.18.2305.22001</Data>
		<Data>646c16cf</Data>
		<Data>ucrtbase.dll</Data>
		<Data>10.0.19041.789</Data>
		<Data>2bd748bf</Data>
		<Data>c0000409</Data>
		<Data>000000000007286e</Data>
		<Data>2b5c</Data>
		<Data>01d98f0dfd26c9b8</Data>
		<Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.18.1421.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data>
		<Data>C:\WINDOWS\System32\ucrtbase.dll</Data>
		<Data>a216b7cb-d516-4fb4-8aed-c5f9d5a4df08</Data>
		<Data>Microsoft.WindowsTerminalPreview_1.18.1421.0_x64__8wekyb3d8bbwe</Data>
		<Data>App</Data>
	</EventData>
</Event>
@sephiroth-j commented on GitHub (May 25, 2023): It happens also when you start a new instance of Windows Terminal Preview (e.g. from the context menu). ![grafik](https://github.com/microsoft/terminal/assets/23166289/419fe4f7-7900-47e6-b071-3f25b1ba6c86) But the Windows Terminal Preview window stays open and is fully usable after closing the Windows dialog. An application error event is logged with the following data. ```xml <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error"/> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2023-05-25T13:37:22.9375479Z"/> <EventRecordID>79999</EventRecordID> <Correlation/> <Execution ProcessID="0" ThreadID="0"/> <Channel>Application</Channel> <Computer>XXXX</Computer> <Security/> </System> <EventData> <Data>WindowsTerminal.exe</Data> <Data>1.18.2305.22001</Data> <Data>646c16cf</Data> <Data>ucrtbase.dll</Data> <Data>10.0.19041.789</Data> <Data>2bd748bf</Data> <Data>c0000409</Data> <Data>000000000007286e</Data> <Data>2b5c</Data> <Data>01d98f0dfd26c9b8</Data> <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.18.1421.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data> <Data>C:\WINDOWS\System32\ucrtbase.dll</Data> <Data>a216b7cb-d516-4fb4-8aed-c5f9d5a4df08</Data> <Data>Microsoft.WindowsTerminalPreview_1.18.1421.0_x64__8wekyb3d8bbwe</Data> <Data>App</Data> </EventData> </Event> ```
claunia commented 2026-01-31 06:58:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 25, 2023):

Do you have focusFollowMouse enabled by any chance? Does disabling that setting fix this? (see #15412)

@zadjii-msft commented on GitHub (May 25, 2023): Do you have `focusFollowMouse` enabled by any chance? Does disabling that setting fix this? (see #15412)
claunia commented 2026-01-31 06:58:45 +00:00
Author
Owner
Copy Link

@evanjs commented on GitHub (May 25, 2023):

Disabling focusFollowMouse appears to resolve the issue for me

@evanjs commented on GitHub (May 25, 2023): Disabling `focusFollowMouse` appears to resolve the issue for me
claunia commented 2026-01-31 06:58:45 +00:00
Author
Owner
Copy Link

@sephiroth-j commented on GitHub (May 26, 2023):

Do you have focusFollowMouse enabled by any chance? Does disabling that setting fix this? (see #15412)

Disabling focusFollowMouse resolves the crash when splitting panes but not when starting another Terminal instance.

@sephiroth-j commented on GitHub (May 26, 2023): > Do you have `focusFollowMouse` enabled by any chance? Does disabling that setting fix this? (see #15412) Disabling `focusFollowMouse` resolves the crash when splitting panes but not when starting another Terminal instance.
claunia commented 2026-01-31 06:58:46 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 26, 2023):

@sephiroth-j You're on Windows 10, yea? My psychic debugging tells me that the crash when starting a second instance is #15410. That's based solely on the observation that the second windowsterminal.exe process crashes, but the first keeps running happily. I don't think there's a workaround for that one currently - though, we should have a hotfix for that soontm

@zadjii-msft commented on GitHub (May 26, 2023): @sephiroth-j You're on Windows 10, yea? My psychic debugging tells me that the crash when starting a second instance is #15410. That's based solely on the observation that the _second_ `windowsterminal.exe` process crashes, but the first keeps running happily. I don't think there's a workaround for that one currently - though, we should have a hotfix for that soon<sup>tm
claunia commented 2026-01-31 06:58:46 +00:00
Author
Owner
Copy Link

@sephiroth-j commented on GitHub (May 26, 2023):

@sephiroth-j You're on Windows 10, yea? My psychic debugging tells me that the crash when starting a second instance is #15410. That's based solely on the observation that the second windowsterminal.exe process crashes, but the first keeps running happily. I don't think there's a workaround for that one currently - though, we should have a hotfix for that soontm

Yes, version 10.0.19045.3031 to be precise. Thanks for pointing out issue #15410, I must have missed that. 🤷

@sephiroth-j commented on GitHub (May 26, 2023): > @sephiroth-j You're on Windows 10, yea? My psychic debugging tells me that the crash when starting a second instance is #15410. That's based solely on the observation that the _second_ `windowsterminal.exe` process crashes, but the first keeps running happily. I don't think there's a workaround for that one currently - though, we should have a hotfix for that soontm Yes, version 10.0.19045.3031 to be precise. Thanks for pointing out issue #15410, I must have missed that. 🤷
claunia commented 2026-01-31 06:58:46 +00:00
Author
Owner
Copy Link

@killshot13 commented on GitHub (May 28, 2023):

Do you have focusFollowMouse enabled by any chance? Does disabling that setting fix this? (see #15412)

Yes, I did, and yes, that resolved the issue. I am closing this issue since the root cause is already being tracked in #15420. Thank you, @zadjii-msft.

@killshot13 commented on GitHub (May 28, 2023): > Do you have `focusFollowMouse` enabled by any chance? Does disabling that setting fix this? (see #15412) Yes, I did, and yes, that resolved the issue. I am closing this issue since the root cause is already being tracked in #15420. Thank you, @zadjii-msft.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Attention Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#19960
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?