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 when closing tab while loading power shell modules #6900

New Issue
Closed
opened 2026-01-31 00:50:00 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 00:50:00 +00:00
Owner
Copy Link

Originally created by @michaelmairegger on GitHub (Mar 16, 2020).

Environment

Windows build number: 10.0.18363.657
Windows Terminal version (if applicable): 0.9.433.0

Steps to reproduce

  • Open new Windows Power Shell Tab
  • Close the tab as soon as the module loading message appears.

Expected behavior

No crash

Actual behavior

Crash of the power shell process.

Originally created by @michaelmairegger on GitHub (Mar 16, 2020). # Environment Windows build number: 10.0.18363.657 Windows Terminal version (if applicable): 0.9.433.0 # Steps to reproduce - Open new Windows Power Shell Tab - Close the tab as soon as the module loading message appears. # Expected behavior No crash # Actual behavior Crash of the power shell process.
claunia added the Resolution-ExternalNeeds-Tag-FixProduct-Powershell labels 2026-01-31 00:50:00 +00:00
claunia commented 2026-01-31 00:50:01 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 16, 2020):

Sorry, is powershell crashing or is terminal crashing?

@DHowett-MSFT commented on GitHub (Mar 16, 2020): Sorry, is _powershell_ crashing or is _terminal_ crashing?
claunia commented 2026-01-31 00:50:02 +00:00
Author
Owner
Copy Link

@michaelmairegger commented on GitHub (Mar 17, 2020):

powershell is crashing but if I do the same steps directly on the powershell the powershell does not crash

@michaelmairegger commented on GitHub (Mar 17, 2020): _powershell_ is crashing but if I do the same steps directly on the powershell the powershell does not crash
claunia commented 2026-01-31 00:50:02 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 17, 2020):

So, all Terminal does is send a standard close event to powershell; there shouldn't be any magic in how it tears down within versus without terminal. It might be worthwhile to file a bug on the powershell repository, as they may have more insight into what's going on.

Thanks!

@DHowett-MSFT commented on GitHub (Mar 17, 2020): So, all Terminal does is send a standard close event to powershell; there shouldn't be any magic in how it tears down within versus without terminal. It might be worthwhile to file a bug on [the powershell repository](https://github.com/powershell/powershell), as they may have more insight into what's going on. Thanks!
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 Product-Powershell 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#6900
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?