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

Crash on new tab/split #7875

New Issue
Closed
opened 2026-01-31 01:14:49 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 01:14:49 +00:00
Owner
Copy Link

Originally created by @schleumer on GitHub (May 2, 2020).

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

Any other software?

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.19041.0 Microsoft Windows NT 10.0.19041.0

Windows Terminal 0.11.1191.0

Steps to reproduce

With version v0.11.1121.0 or greater.

Create a new tab via CTRL+SHIFT+T or splitting ALT+SHIFT+(plus/minus), with any kind of terminal, cmd, powershell or wsl.

Expected behavior

Do not crash.

Actual behavior

It crashes. Before crash, terminal screen becomes black with no output.

Originally created by @schleumer on GitHub (May 2, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Windows Terminal version (if applicable): Any other software? ``` ``` Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0 ``` Windows Terminal 0.11.1191.0 # Steps to reproduce <!-- A description of how to trigger this bug. --> With version v0.11.1121.0 or greater. Create a new tab via CTRL+SHIFT+T or splitting ALT+SHIFT+(plus/minus), with any kind of terminal, cmd, powershell or wsl. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Do not crash. # Actual behavior <!-- What's actually happening? --> It crashes. Before crash, terminal screen becomes black with no output.
claunia added the Resolution-ExternalNeeds-Tag-FixNeeds-Attention labels 2026-01-31 01:14:49 +00:00
claunia commented 2026-01-31 01:14:50 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 2, 2020):

/feedback

@DHowett-MSFT commented on GitHub (May 2, 2020): /feedback
claunia commented 2026-01-31 01:14:50 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 2, 2020):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

image image

@ghost commented on GitHub (May 2, 2020): Hi there!<br><br>Can you please send us feedback with the Feedback Hub with this issue and 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/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-31 01:14:50 +00:00
Author
Owner
Copy Link

@schleumer commented on GitHub (May 2, 2020):

https://aka.ms/AA8b4qo

@schleumer commented on GitHub (May 2, 2020): https://aka.ms/AA8b4qo
claunia commented 2026-01-31 01:14:50 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 4, 2020):

It appears as though Terminal is crashing because of something called "RivaTuner". When using hook libraries that load themselves into other applications, you're taking the stability of those applications into your own hands.

@DHowett-MSFT commented on GitHub (May 4, 2020): It appears as though Terminal is crashing because of something called "RivaTuner". When using hook libraries that load themselves into other applications, you're taking the stability of those applications into your own hands.
claunia commented 2026-01-31 01:14:50 +00:00
Author
Owner
Copy Link

@valentinmk commented on GitHub (Oct 15, 2020):

Same is here
Exiting MSI Afterburner software fixes crashing terminal on a new tab.

@valentinmk commented on GitHub (Oct 15, 2020): Same is here Exiting MSI Afterburner software fixes crashing terminal on a new tab.
claunia commented 2026-01-31 01:14:50 +00:00
Author
Owner
Copy Link

@KidesLeo commented on GitHub (Oct 19, 2020):

Fixed mine too. Thanks.

@KidesLeo commented on GitHub (Oct 19, 2020): Fixed mine too. Thanks.
claunia commented 2026-01-31 01:14:51 +00:00
Author
Owner
Copy Link

@scorsy63 commented on GitHub (Oct 22, 2020):

I had no idea MSI Afterburner/Riva Tuner was causing the crashes. To fix the issue without having to close MSI/Riva Tuner -

Open Riva Tuner, click the "Add" button at the bottom left corner, to add new profile properties.

Find Windows Terminal in "C:\Program Files\WindowsApps"

There might be older versions of WindowsTerminal in there, make sure to open the current version you're using.

There's 4 .exe files inside, open each one and set "Application detection level" to "None".

@scorsy63 commented on GitHub (Oct 22, 2020): I had no idea MSI Afterburner/Riva Tuner was causing the crashes. To fix the issue without having to close MSI/Riva Tuner - Open Riva Tuner, click the "Add" button at the bottom left corner, to add new profile properties. Find Windows Terminal in "C:\Program Files\WindowsApps" There might be older versions of WindowsTerminal in there, make sure to open the current version you're using. There's 4 .exe files inside, open each one and set "Application detection level" to "None".
claunia commented 2026-01-31 01:14:51 +00:00
Author
Owner
Copy Link

@FM1337 commented on GitHub (Apr 3, 2021):

I had no idea MSI Afterburner/Riva Tuner was causing the crashes. To fix the issue without having to close MSI/Riva Tuner -

Open Riva Tuner, click the "Add" button at the bottom left corner, to add new profile properties.

Find Windows Terminal in "C:\Program Files\WindowsApps"

There might be older versions of WindowsTerminal in there, make sure to open the current version you're using.

There's 4 .exe files inside, open each one and set "Application detection level" to "None".

Thanks mate, this was driving me bonkers, I had to open up a new terminal window each time I wanted to use the terminal because it would literally crash on each new tab.

@FM1337 commented on GitHub (Apr 3, 2021): > I had no idea MSI Afterburner/Riva Tuner was causing the crashes. To fix the issue without having to close MSI/Riva Tuner - > > Open Riva Tuner, click the "Add" button at the bottom left corner, to add new profile properties. > > Find Windows Terminal in "C:\Program Files\WindowsApps" > > There might be older versions of WindowsTerminal in there, make sure to open the current version you're using. > > There's 4 .exe files inside, open each one and set "Application detection level" to "None". Thanks mate, this was driving me bonkers, I had to open up a new terminal window each time I wanted to use the terminal because it would literally crash on each new tab.
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 Needs-Attention Needs-Tag-Fix Resolution-External
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#7875
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?