starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 08:24:54 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Windows Terminal crashes (Vanishes with no errors) when large font sizes are used #22534

New Issue
Closed
opened 2026-01-31 08:16:02 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 08:16:02 +00:00
Owner
Copy Link

Originally created by @feoh on GitHub (Nov 12, 2024).

Windows Terminal version

1.21.2911.0

Windows build number

10.0.22631.0

Other Software

The bug sometimes manifests when I'm running Neovim although it's also quite common from just the terminal itself, either in WSL2 running stock Ubuntu or in Powershell on the native Windows host side.

Steps to reproduce

Open Terminal. Hit Ctrl+ 5 times to boost font size to my ludicrously large default :)

Open a text based editor, stream some text to the terminal. I can't really pin down the behavior that triggers it very well or I'd take a screen recording.

This issue has happened in the past but was fixed and vanished for a while. I had previously been tracking it in https://github.com/microsoft/terminal/issues/8730

Expected Behavior

I expect Terminal not to just vanish taking my editing session, command session or whatever else I'm working on with it. This is the worst kind of failure in a terminal program IMO.

Even if it just hard crashed I could maybe at least just copy what my current state was, vanishing without a trace is tough.

Actual Behavior

Terminal vanishes with no error in mid stream, sometimes while typing, sometimes while displaying streamed text.

Originally created by @feoh on GitHub (Nov 12, 2024). ### Windows Terminal version 1.21.2911.0 ### Windows build number 10.0.22631.0 ### Other Software The bug sometimes manifests when I'm running Neovim although it's also quite common from just the terminal itself, either in WSL2 running stock Ubuntu or in Powershell on the native Windows host side. ### Steps to reproduce Open Terminal. Hit Ctrl+ 5 times to boost font size to my ludicrously large default :) Open a text based editor, stream some text to the terminal. I can't really pin down the behavior that triggers it very well or I'd take a screen recording. This issue has happened in the past but was fixed and vanished for a while. I had previously been tracking it in https://github.com/microsoft/terminal/issues/8730 ### Expected Behavior I expect Terminal not to just vanish taking my editing session, command session or whatever else I'm working on with it. This is the worst kind of failure in a terminal program IMO. Even if it just hard crashed I could maybe at least just copy what my current state was, vanishing without a trace is tough. ### Actual Behavior Terminal vanishes with no error in mid stream, sometimes while typing, sometimes while displaying streamed text.
claunia added the Needs-TriageIssue-BugNeeds-AttentionProduct-Terminal labels 2026-01-31 08:16:02 +00:00
claunia commented 2026-01-31 08:16:03 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Nov 20, 2024):

Thanks for filing! Could you please capture a dump file using this guide /? https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically

@carlos-zamora commented on GitHub (Nov 20, 2024): Thanks for filing! Could you please capture a dump file using this guide /? https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically
claunia commented 2026-01-31 08:16:03 +00:00
Author
Owner
Copy Link

@feoh commented on GitHub (Nov 20, 2024):

Happy to. It's frustratingly irregular, it won't happen for a while, and then the window will vanish very shortly after opening a new tab.

Thanks for taking a look!

@feoh commented on GitHub (Nov 20, 2024): Happy to. It's frustratingly irregular, it won't happen for a while, and then the window will vanish very shortly after opening a new tab. Thanks for taking a look!
claunia commented 2026-01-31 08:16:04 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 20, 2024):

If you have any historical entries in your Event Viewer for this crash, that may help too! :)

@DHowett commented on GitHub (Nov 20, 2024): If you have any historical entries in your Event Viewer for this crash, that may help too! :)
claunia commented 2026-01-31 08:16:04 +00:00
Author
Owner
Copy Link

@feoh commented on GitHub (Nov 20, 2024):

@DHowett Any clues for the clueless around what I'd be searching for? Pardon I'm a bit Event Viewer clueless.

Thanks so much again for taking a look.

@feoh commented on GitHub (Nov 20, 2024): @DHowett Any clues for the clueless around what I'd be searching for? Pardon I'm a bit Event Viewer clueless. Thanks so much again for taking a look.
claunia commented 2026-01-31 08:16:04 +00:00
Author
Owner
Copy Link

@feoh commented on GitHub (Dec 3, 2024):

It just happened again and no new dumps appeared.

I wish I had a way to make it repro consistently. Worst bug report ever :(

@feoh commented on GitHub (Dec 3, 2024): It just happened again and no new dumps appeared. I wish I had a way to make it repro consistently. Worst bug report ever :(
claunia commented 2026-01-31 08:16:04 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Dec 4, 2024):

Any clues for the clueless around what I'd be searching for? Pardon I'm a bit Event Viewer clueless.

Sorry for not responding earlier. When an application crashes it should look like this:
Image

It seems we haven't mentioned it yet, but please ensure you're using the very latest GPU drivers, straight from the Intel/AMD/Nvidia website. (If you don't know where to find them, let me know what GPU you're using and I'll find it for you.)

@lhecker commented on GitHub (Dec 4, 2024): > Any clues for the clueless around what I'd be searching for? Pardon I'm a bit Event Viewer clueless. Sorry for not responding earlier. When an application crashes it should look like this: ![Image](https://github.com/user-attachments/assets/79641bee-9aa8-4f7a-927a-2f8bddcb8a28) It seems we haven't mentioned it yet, but please ensure you're using the very latest GPU drivers, straight from the Intel/AMD/Nvidia website. (If you don't know where to find them, let me know what GPU you're using and I'll find it for you.)
claunia commented 2026-01-31 08:16:05 +00:00
Author
Owner
Copy Link

@feoh commented on GitHub (Dec 9, 2024):

After some significant local testing I've determined that the problem was actually a corrupted Ubuntu 20.04 image that was causing the crash.

Sorry about the mis-identified bug folks and thank you for your time and attention! Windows Terminal and the new console host are amazing!

@feoh commented on GitHub (Dec 9, 2024): After some significant local testing I've determined that the problem was actually a corrupted Ubuntu 20.04 image that was causing the crash. Sorry about the mis-identified bug folks and thank you for your time and attention! Windows Terminal and the new console host are *amazing*!
claunia commented 2026-01-31 08:16:05 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 9, 2024):

Wow! I'm not sure how that all fit together, but thank you so much for root causing it and coming back to tell us! 🙂

@DHowett commented on GitHub (Dec 9, 2024): Wow! I'm not sure how that all fit together, but thank you so much for root causing it and coming back to tell us! 🙂
claunia commented 2026-01-31 08:16:05 +00:00
Author
Owner
Copy Link

@feoh commented on GitHub (Dec 10, 2024):

Absolutely.

My reasoning:

  • I noticed that the vanishing window ONLY happened when I was trying to use my Ubuntu 20.04 WSL2 distro
  • I had the idea to try and see if the failure happened when I invoked the distro from the Powershell wsl command, which it did. So I could run wsl -d Ubuntu-20.04 or similar, and after a couple of command line invocations the WSL session would terminate and I'd be back in Powershell.
  • Given the above, I was reasonably sure the distro was faulty. So I blew it away completely and re-installed from scratch (This is a special purpose distro I'm only using to work on OpenEdX legacy issues so no harm done)
  • The issue stopped recurring after nuke & pave
@feoh commented on GitHub (Dec 10, 2024): Absolutely. My reasoning: * I noticed that the vanishing window ONLY happened when I was trying to use my Ubuntu 20.04 WSL2 distro * I had the idea to try and see if the failure happened when I invoked the distro from the Powershell `wsl` command, which it did. So I could run `wsl -d Ubuntu-20.04` or similar, and after a couple of command line invocations the WSL session would terminate and I'd be back in Powershell. * Given the above, I was reasonably sure the distro was faulty. So I blew it away completely and re-installed from scratch (This is a special purpose distro I'm only using to work on OpenEdX legacy issues so no harm done) * The issue stopped recurring after nuke & pave
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 Product-Terminal
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#22534
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?