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

Opening a second powershell and immediately closing it crashes terminal #2084

New Issue
Closed
opened 2026-01-30 22:46:22 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 22:46:22 +00:00
Owner
Copy Link

Originally created by @riskysciolism on GitHub (Jun 24, 2019).

Environment

Windows build number: Version 10.0.18362.175
Terminal Version: 0.2.1715.0

Steps to reproduce

Open Windows Terminal which defaults to an open tab with powershell.
Open a second tab with powershell, and immediately close it.
Terminal crashes/freezes.

Expected behavior

The recently opened tab simply closes

Actual behavior

Tab and the complete Terminal freezes. Need to ALT + Ctrl + Delete.

Originally created by @riskysciolism on GitHub (Jun 24, 2019). # Environment ```none Windows build number: Version 10.0.18362.175 Terminal Version: 0.2.1715.0 ``` # Steps to reproduce Open Windows Terminal which defaults to an open tab with powershell. Open a second tab with powershell, and immediately close it. Terminal crashes/freezes. # Expected behavior The recently opened tab simply closes # Actual behavior Tab and the complete Terminal freezes. Need to ALT + Ctrl + Delete.
claunia added the Needs-TriageNeeds-Tag-FixResolution-Duplicate labels 2026-01-30 22:46:22 +00:00
claunia commented 2026-01-30 22:46:23 +00:00
Author
Owner
Copy Link

@mcpiroman commented on GitHub (Jun 24, 2019):

I had similar issue when I set "commandline" : "powershell -c dir" (which caused terminal to run dir and then close), but after a while it stoped crashing.

EDIT: I can reproduce it now on release mode. Just set commandline to execute something fast, like dir or cd .., either directly or via powershell -c or cmd /C.

@mcpiroman commented on GitHub (Jun 24, 2019): I had similar issue when I set `"commandline" : "powershell -c dir"` (which caused terminal to run `dir` and then close), but after a while it stoped crashing. EDIT: I can reproduce it now on release mode. Just set commandline to execute something fast, like `dir` or `cd ..`, either directly or via `powershell -c` or `cmd /C`.
claunia commented 2026-01-30 22:46:23 +00:00
Author
Owner
Copy Link

@JushBJJ commented on GitHub (Jun 24, 2019):

That seems like an issue within the terminal itself depending on how fast your computer is. But the issue really is visible when you open powershell.

@JushBJJ commented on GitHub (Jun 24, 2019): That seems like an issue within the terminal itself depending on how fast your computer is. But the issue really is visible when you open powershell.
claunia commented 2026-01-30 22:46:23 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 27, 2019):

Probably the same as #1445

@DHowett-MSFT commented on GitHub (Jun 27, 2019): Probably the same as #1445
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-Tag-Fix Needs-Triage Resolution-Duplicate
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#2084
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?