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

Terminal with PowerShell prompt crashes on input after maximizing and restoring window #1643

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

Originally created by @nlebeck on GitHub (Jun 12, 2019).

This bug might be related to #175, #1095, or #1206. The specific conditions causing the bug here are different enough from the conditions described in those issues that I thought it might be worth filing a separate issue.

Environment

Windows build number: 10.0.18362.145
Windows Terminal version (if applicable): built from source at commit e20dfb8

Visual Studio Community 2019 (Version 16.1.3)

Dell Precision T5810
CPU: Xeon E5-1650 v3 @3.50GHz
RAM: 16GB

Steps to reproduce

  1. Launch CascadiaPackage (x64 configuration) from Visual Studio. A PowerShell prompt will appear.
  2. Type ls into the prompt and hit enter.
  3. Maximize the window.
  4. Type ls and hit enter again.
  5. Restore the window.
  6. Type ls and hit enter a third time.

Expected behavior

ls works correctly the third time.

Actual behavior

The terminal crashes after entering ls the third time. I've seen two different types of error message. In one case, the terminal prints the following text in red and then exits right afterwards:

out-lineoutput : The Win32 internal error "The parameter is incorrect" 0x57 occurred while writing to the console

In another case, Visual Studio displays a dialog box with the following text (identical to the dialog box from #1095):

Debug Error!

Program:
...l\src\cascadia\CascadiaPackage\bin\x64\Debug\AppX\conhost.exe

abort() has been called

(Press Retry to debug the application)

Furthermore, after encountering the second error case, the solution sometimes ends up in a state where I can no longer successfully launch CascadiaPackage. Every time I try to start it, I get the same dialog box with the same error message. This has happened to me twice now, and the only solution I've found is to delete the repo and re-clone it. (Even git clean -dix didn't get it working again.)

I first encountered this bug when running with multiple PowerShell tabs open, and in that case, only the active tab would crash (with the first type of error message).

Originally created by @nlebeck on GitHub (Jun 12, 2019). <!-- 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. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> This bug might be related to #175, #1095, or #1206. The specific conditions causing the bug here are different enough from the conditions described in those issues that I thought it might be worth filing a separate issue. # Environment ```none Windows build number: 10.0.18362.145 Windows Terminal version (if applicable): built from source at commit e20dfb8 Visual Studio Community 2019 (Version 16.1.3) Dell Precision T5810 CPU: Xeon E5-1650 v3 @3.50GHz RAM: 16GB ``` # Steps to reproduce 1. Launch CascadiaPackage (x64 configuration) from Visual Studio. A PowerShell prompt will appear. 2. Type `ls` into the prompt and hit enter. 3. Maximize the window. 4. Type `ls` and hit enter again. 5. Restore the window. 6. Type `ls` and hit enter a third time. # Expected behavior `ls` works correctly the third time. # Actual behavior The terminal crashes after entering `ls` the third time. I've seen two different types of error message. In one case, the terminal prints the following text in red and then exits right afterwards: out-lineoutput : The Win32 internal error "The parameter is incorrect" 0x57 occurred while writing to the console In another case, Visual Studio displays a dialog box with the following text (identical to the dialog box from #1095): Debug Error! Program: ...l\src\cascadia\CascadiaPackage\bin\x64\Debug\AppX\conhost.exe abort() has been called (Press Retry to debug the application) Furthermore, after encountering the second error case, the solution sometimes ends up in a state where I can no longer successfully launch CascadiaPackage. Every time I try to start it, I get the same dialog box with the same error message. This has happened to me twice now, and the only solution I've found is to delete the repo and re-clone it. (Even `git clean -dix` didn't get it working again.) I first encountered this bug when running with multiple PowerShell tabs open, and in that case, only the active tab would crash (with the first type of error message).
claunia commented 2026-01-30 22:32:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 13, 2019):

I'd rather leave this open to make sure this scenario is fixed than prematurely resolving as a dupe. It feels different enough from the others, and has great repro steps.

I have no idea why the second error case would totally break your Terminal install though...

@zadjii-msft commented on GitHub (Jun 13, 2019): I'd rather leave this open to make sure this scenario is fixed than prematurely resolving as a dupe. It feels different enough from the others, and has great repro steps. I have _no idea_ why the second error case would totally break your Terminal install though...
claunia commented 2026-01-30 22:32:49 +00:00
Author
Owner
Copy Link

@nlebeck commented on GitHub (Aug 8, 2019):

FYI, it looks like this bug is fixed in the latest Windows Store build (version 0.3.2171.0).

@nlebeck commented on GitHub (Aug 8, 2019): FYI, it looks like this bug is fixed in the latest Windows Store build (version 0.3.2171.0).
claunia commented 2026-01-30 22:32:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 8, 2019):

@nlebeck thanks for confirming! I believe #2149 was the fix for this one.

@zadjii-msft commented on GitHub (Aug 8, 2019): @nlebeck thanks for confirming! I believe #2149 was the fix for this one.
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 Area-Interaction Issue-Bug Product-Conhost Product-Terminal Resolution-Fix-Available
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#1643
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?