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

Crash when opening a new tab or window, or any non-default profile #19980

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

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

Windows Terminal version

1.18.1421.0

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

Open two tabs or two windows.

Expected Behavior

Two tabs are opened and can be used.

Actual Behavior

Opening the second tab or window triggers a crash of the entire application, taking both tabs/windows with it.

Windows Terminal 1.16.10261.0 with the same configuration works as expected.

Originally created by @sboukortt on GitHub (May 25, 2023). ### Windows Terminal version 1.18.1421.0 ### Windows build number 10.0.19045.0 ### Other Software _No response_ ### Steps to reproduce Open two tabs or two windows. ### Expected Behavior Two tabs are opened and can be used. ### Actual Behavior Opening the second tab or window triggers a crash of the entire application, taking both tabs/windows with it. Windows Terminal 1.16.10261.0 with the same configuration works as expected.
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 06:59:20 +00:00
claunia commented 2026-01-31 06:59:22 +00:00
Author
Owner
Copy Link

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

I saw an open issue that I thought might be related but the discussion suggests that that other issue is specific to when focusFollowMouse is enabled, and I have it disabled.

@sboukortt commented on GitHub (May 25, 2023): I saw an open issue that I thought might be related but the discussion suggests that that other issue is specific to when `focusFollowMouse` is enabled, and I have it disabled.
claunia commented 2026-01-31 06:59:23 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (May 26, 2023):

Yesterday, when running a debug build off of main, I also had it crashing, and it was due to GetRootPane() returning nullptr right here:
3c3b1aac02/src/cascadia/TerminalApp/TerminalPage.cpp (L3355-L3360)

Curiously this issue has never occurred before on my PC.

@lhecker commented on GitHub (May 26, 2023): Yesterday, when running a debug build off of main, I also had it crashing, and it was due to `GetRootPane()` returning `nullptr` right here: https://github.com/microsoft/terminal/blob/3c3b1aac02320f49f6887f08e6d6d1d56132b1ef/src/cascadia/TerminalApp/TerminalPage.cpp#L3355-L3360 Curiously this issue has never occurred before on my PC.
claunia commented 2026-01-31 06:59:23 +00:00
Author
Owner
Copy Link

@sboukortt commented on GitHub (May 26, 2023):

Oh, interesting, thanks. Is it something that would be reasonably easy to bisect?

@sboukortt commented on GitHub (May 26, 2023): Oh, interesting, thanks. Is it something that would be reasonably easy to bisect?
claunia commented 2026-01-31 06:59:23 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (May 26, 2023):

It's not really something that needs to be bisected, because as far as I can tell, the exact same code ran perfectly fine for the last year on my PC. Rather, I suspect that some unrelated change has changed the order of initialization slightly to allow for visibility change messages to arrive sooner. This could've for instance happened, because I made the startup of Windows Terminal vastly (>2x) faster.
Although we'll only know if you're victim of the same issue if you either debug Windows Terminal yourself (for instance via WinDbg; you can find it in the App Store) or capture a crash dump for us (see here). Otherwise, we'll automatically receive minidumps of this crash within a week or so, if you have telemetry enabled.

@lhecker commented on GitHub (May 26, 2023): It's not really something that needs to be bisected, because as far as I can tell, the exact same code ran perfectly fine for the last year on my PC. Rather, I suspect that some unrelated change has changed the order of initialization slightly to allow for visibility change messages to arrive sooner. This could've for instance happened, because I made the startup of Windows Terminal _vastly_ (>2x) faster. Although we'll only know if you're victim of the same issue if you either debug Windows Terminal yourself (for instance via WinDbg; you can find it in the App Store) or capture a crash dump for us (see [here](https://github.com/microsoft/terminal/wiki/Toubleshooting-Tips#capture-automatically)). Otherwise, we'll automatically receive minidumps of this crash within a week or so, if you have telemetry enabled.
claunia commented 2026-01-31 06:59:24 +00:00
Author
Owner
Copy Link

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

Yea, we'll need a stack or something to investigate here.

If you file /feedback with the Feedback Hub, we might be able to reverse engineer that in the backend and find crashes that have already happened. Unlikely, but worth a shot.

If it repros consistently though, then just trying to repro it with the feedback hub's "Recreate my problem" recorder should grab the dump.
image

@zadjii-msft commented on GitHub (May 26, 2023): Yea, we'll need a stack or something to investigate here. If you file /feedback with the Feedback Hub, we _might_ be able to reverse engineer that in the backend and find crashes that have already happened. Unlikely, but worth a shot. If it repros consistently though, then just trying to repro it with the feedback hub's "Recreate my problem" recorder _should_ grab the dump. ![image](https://github.com/microsoft/terminal/assets/18356694/035365d2-8c0c-4782-8331-d20e52ef2256)
claunia commented 2026-01-31 06:59:24 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (May 26, 2023):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?

Thanks!

image

image

image

@microsoft-github-policy-service[bot] commented on GitHub (May 26, 2023): Hi there!<br><br>Can you please send us feedback with the [Feedback Hub](https://support.microsoft.com/en-us/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332) with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18356694/140811502-a068f78b-89d2-4587-925a-73e19652b830.png)<br><br>![image](https://user-images.githubusercontent.com/18356694/140811557-cdc22a0f-fa6a-4f6a-953e-73b51f5548a3.png)<br><br>![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-31 06:59:25 +00:00
Author
Owner
Copy Link

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

Same thing is happening for me. Normally it's intermittent—usually, I can open a new tab without issue. I'd say that the issue manifests maybe 20% of the time. Luckily, it happened every single time when recording it with Feedback Hub, a Vorführeffekt in my favor for a change 😂

@dziban303 commented on GitHub (May 28, 2023): Same thing is happening for me. Normally it's intermittent—usually, I can open a new tab without issue. I'd say that the issue manifests maybe 20% of the time. Luckily, it happened every single time when recording it with Feedback Hub, a Vorführeffekt in my favor for a change 😂
claunia commented 2026-01-31 06:59:25 +00:00
Author
Owner
Copy Link

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

@dziban303 can you share the Feedback Hub link here?

@zadjii-msft commented on GitHub (May 28, 2023): @dziban303 can you share the Feedback Hub link here?
claunia commented 2026-01-31 06:59:25 +00:00
Author
Owner
Copy Link

@dziban303 commented on GitHub (May 29, 2023):

Hey @zadjii-msft sorry. Here's the link https://aka.ms/AAkzyij

@dziban303 commented on GitHub (May 29, 2023): Hey @zadjii-msft sorry. Here's the link https://aka.ms/AAkzyij
claunia commented 2026-01-31 06:59:25 +00:00
Author
Owner
Copy Link

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

I won't be able to take a look till tomorrow at the earliest, but as a sanity check, does https://github.com/microsoft/terminal/releases/tag/v1.18.1462.0 work? That has some hotfixes for... kinda a lot of bugs...

@zadjii-msft commented on GitHub (May 29, 2023): I won't be able to take a look till tomorrow at the earliest, but as a sanity check, does https://github.com/microsoft/terminal/releases/tag/v1.18.1462.0 work? That has some hotfixes for... kinda a lot of bugs...
claunia commented 2026-01-31 06:59:25 +00:00
Author
Owner
Copy Link

@dziban303 commented on GitHub (May 29, 2023):

Thanks, it was literally installing via the Store when you sent that. I'll give it a whirl later tonight. Cheers

@dziban303 commented on GitHub (May 29, 2023): Thanks, it was literally installing via the Store when you sent that. I'll give it a whirl later tonight. Cheers
claunia commented 2026-01-31 06:59:26 +00:00
Author
Owner
Copy Link

@sboukortt commented on GitHub (May 29, 2023):

Sadly, it still reproduces for me. It also seems not to always respect the window transparency I have set, and it crashes when going to “Settings” -> (“Profiles” ->) “Defaults” -> “Appearance” where one would set it. Could that be related?

I tried to file feedback with the Feedback Hub but couldn’t quite figure out whether it would record crash data for Terminal Preview if I select “Terminal” as the app (Terminal Preview isn’t offered as a choice). Does it?

@sboukortt commented on GitHub (May 29, 2023): Sadly, it still reproduces for me. It also seems not to always respect the window transparency I have set, and it crashes when going to “Settings” -> (“Profiles” ->) “Defaults” -> “Appearance” where one would set it. Could that be related? I tried to file feedback with the Feedback Hub but couldn’t quite figure out whether it would record crash data for Terminal _Preview_ if I select “Terminal” as the app (Terminal Preview isn’t offered as a choice). Does it?
claunia commented 2026-01-31 06:59:26 +00:00
Author
Owner
Copy Link

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

Okay so ai was able to find a dump from @dziban303's machine (even if Feedback Hub wasn't the most cooperative). It looks like you're hitting the "focusFollowMouse": true crash. That was tracked in #15412, and should be fixed in https://github.com/microsoft/terminal/releases/tag/v1.18.1462.0.

@sboukortt - you've got that setting disabled, so presumably you're seeing something new. Can you file the same Feedback Hub steps above/? That should help us find the dump on the backend.

@zadjii-msft commented on GitHub (May 30, 2023): Okay so ai was able to find a dump from @dziban303's machine (even if Feedback Hub wasn't the _most_ cooperative). It looks like you're hitting the `"focusFollowMouse": true` crash. That was tracked in #15412, and should be fixed in https://github.com/microsoft/terminal/releases/tag/v1.18.1462.0. @sboukortt - you've got that setting disabled, so presumably you're seeing something new. Can you file the same Feedback Hub steps above/? That should help us find the dump on the backend.
claunia commented 2026-01-31 06:59:26 +00:00
Author
Owner
Copy Link

@sboukortt commented on GitHub (May 31, 2023):

I am not sure what changed but it doesn’t seem to be happening anymore? That’s still with v1.18.1462.0.

The main change I can think of that could possibly have to do with this is that I upgraded my graphics driver (NVIDIA) to 535.98, from the previous “studio” driver (I don’t remember which version that was).

@sboukortt commented on GitHub (May 31, 2023): I am not sure what changed but it doesn’t seem to be happening anymore? That’s still with v1.18.1462.0. The main change I can think of that could possibly have to do with this is that I upgraded my graphics driver (NVIDIA) to 535.98, from the previous “studio” driver (I don’t remember which version that was).
claunia commented 2026-01-31 06:59:26 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 1, 2023):

Wow, okay, that's weird. Since we lost our repro, I'm gonna close this one out. Please don't hesitate to yell at us if it comes back!

@DHowett commented on GitHub (Jun 1, 2023): _Wow,_ okay, that's weird. Since we lost our repro, I'm gonna close this one out. Please don't hesitate to yell at us if it comes back!
claunia commented 2026-01-31 06:59:26 +00:00
Author
Owner
Copy Link

@sboukortt commented on GitHub (Jun 22, 2023):

For some reason, it seems to be happening again since my last reboot. (I usually use hybrid shutdown / “fast startup” rather than a full reboot.) The version of Terminal Preview is still v1.18.1462.0.

I am getting the impression that there is something that causes it to either happen reliably or not at all after every reboot, which is rather mysterious. Thankfully, if that is the case, it means I have until my next full reboot to figure out how to get a proper stacktrace.

@sboukortt commented on GitHub (Jun 22, 2023): For some reason, it seems to be happening again since my last reboot. (I usually use hybrid shutdown / “fast startup” rather than a full reboot.) The version of Terminal Preview is still v1.18.1462.0. I am getting the impression that there is something that causes it to either happen reliably or not at all after every reboot, which is rather mysterious. Thankfully, if that is the case, it means I have until my next full reboot to figure out how to get a proper stacktrace.
claunia commented 2026-01-31 06:59:27 +00:00
Author
Owner
Copy Link

@sboukortt commented on GitHub (Jul 25, 2023):

I still haven’t gotten around to doing that, but for what it’s worth, the other day, I updated my GPU driver and it seems to have crashed Terminal Preview but not Terminal.

@sboukortt commented on GitHub (Jul 25, 2023): I still haven’t gotten around to doing that, but for what it’s worth, the other day, I updated my GPU driver and it seems to have crashed Terminal Preview but not Terminal.
claunia commented 2026-01-31 06:59:27 +00:00
Author
Owner
Copy Link

@zhangjy859 commented on GitHub (May 13, 2024):

Hi @sboukortt，

I also have the same issue after a system reboot, Could you please give me some suggestions? I have feedback with feedback hub

@zhangjy859 commented on GitHub (May 13, 2024): Hi @sboukortt， I also have the same issue after a system reboot, Could you please give me some suggestions? I have feedback with feedback hub
claunia commented 2026-01-31 06:59:27 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 13, 2024):

@zhangjy859 Do you have MacType installed by any chance? If so, go update it. Older versions of that will crash the Terminal.

If not, could you share the link to your feedback in Feedback Hub here in this thread? Thanks!

@zadjii-msft commented on GitHub (May 13, 2024): @zhangjy859 Do you have MacType installed by any chance? If so, go update it. Older versions of that will crash the Terminal. If not, could you share the link to your feedback in Feedback Hub here in this thread? Thanks!
claunia commented 2026-01-31 06:59:27 +00:00
Author
Owner
Copy Link

@zhangjy859 commented on GitHub (May 13, 2024):

@zhangjy859 Do you have MacType installed by any chance? If so, go update it. Older versions of that will crash the Terminal.

If not, could you share the link to your feedback in Feedback Hub here in this thread? Thanks!

Yeah, I have MacType, I have tried update it and uninstall it, but not work, however, as @sboukortt's comment, I updated my GPU graphic driver, Its ok.

Interestingly, this is my workstation and for a considerable amount of time, it had a fixed version of Windows Terminal, MacType, and graphics drivers, and they worked without any issues. I'm not sure why there was a change after a restart. In any case, updating the graphics drivers could be helpful.

Thank you for your prompt reply and assistance.

@zhangjy859 commented on GitHub (May 13, 2024): > @zhangjy859 Do you have MacType installed by any chance? If so, go update it. Older versions of that will crash the Terminal. > > If not, could you share the link to your feedback in Feedback Hub here in this thread? Thanks! Yeah, I have MacType, I have tried update it and uninstall it, but not work, however, as @sboukortt's comment, I updated my GPU graphic driver, Its ok. Interestingly, this is my workstation and for a considerable amount of time, it had a fixed version of Windows Terminal, MacType, and graphics drivers, and they worked without any issues. I'm not sure why there was a change after a restart. In any case, updating the graphics drivers could be helpful. Thank you for your prompt reply and assistance.
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#19980
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?