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 dump attached - hang then crash after locking console then connecting via RDP #20726

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

Originally created by @mailinglists35 on GitHub (Oct 23, 2023).

Windows Terminal version

don't remember, something recent but I've updated today

Windows build number

10.0.19045.3448

Other Software

WSL1

Steps to reproduce

not sure

Expected Behavior

not sure if reproductible.

I frequently alternate console and RDP usage of this workstation.
Usually it's just the message about something and I click a button named "Resume", then everything works ("Resume" appears when I connect to console after disconnected from RDP)
Today I left console then later connected via RDP. it initially showed unresponsive tab, then whole app hanged, then crashed entire terminal eventually

Managed to get a dump using Create dump file in System Informer (formerly known as Process Hacker)

Attached if developers interested in having a look

Actual Behavior

link password available on request

https://emma.cloud.tabdigital.eu/s/9Ms4q5fbgJiB7Bb

Originally created by @mailinglists35 on GitHub (Oct 23, 2023). ### Windows Terminal version don't remember, something recent but I've updated today ### Windows build number 10.0.19045.3448 ### Other Software WSL1 ### Steps to reproduce not sure ### Expected Behavior not sure if reproductible. I frequently alternate console and RDP usage of this workstation. Usually it's just the message about something and I click a button named "Resume", then everything works ("Resume" appears when I connect to console after disconnected from RDP) Today I left console then later connected via RDP. it initially showed unresponsive tab, then whole app hanged, then crashed entire terminal eventually Managed to get a dump using Create dump file in System Informer (formerly known as Process Hacker) Attached if developers interested in having a look ### Actual Behavior link password available on request https://emma.cloud.tabdigital.eu/s/9Ms4q5fbgJiB7Bb
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 07:22:19 +00:00
claunia commented 2026-01-31 07:22:20 +00:00
Author
Owner
Copy Link

@mailinglists35 commented on GitHub (Oct 23, 2023):

the dump was taken before crashing, while the app was entirely unresponsive

@mailinglists35 commented on GitHub (Oct 23, 2023): the dump was taken before crashing, while the app was entirely unresponsive
claunia commented 2026-01-31 07:22:20 +00:00
Author
Owner
Copy Link

@mailinglists35 commented on GitHub (Oct 23, 2023):

link is passworded because I don't know what tons of private data could be there. you have to be a ms dev to ask for it.,

@mailinglists35 commented on GitHub (Oct 23, 2023): link is passworded because I don't know what tons of private data could be there. you have to be a ms dev to ask for it.,
claunia commented 2026-01-31 07:22:20 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 23, 2023):

Almost 100% chance, this is /dup #3915

@zadjii-msft commented on GitHub (Oct 23, 2023): Almost 100% chance, this is /dup #3915
claunia commented 2026-01-31 07:22:21 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Oct 23, 2023):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Oct 23, 2023): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
claunia commented 2026-01-31 07:22:21 +00:00
Author
Owner
Copy Link

@mailinglists35 commented on GitHub (Oct 24, 2023):

uhm, when I said I updated, I meant I updated after the crash, so that explains why I don't remember the version that crashed.

100% this is NOT update related, as I configured auto update to never happen.

@zadjii-msft

@mailinglists35 commented on GitHub (Oct 24, 2023): uhm, when I said I updated, I meant I updated **after** the crash, so that explains why I don't remember the version that crashed. 100% this is NOT update related, as I configured auto update to never happen. @zadjii-msft
claunia commented 2026-01-31 07:22:21 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 24, 2023):

Oh, no the Windows Store will literally inject a thread into an app to kill it to install an update for that app if it wasn't ever closed within some window after an update is available. The manifest entry to prevent that behavior only got added in the latest Windows 11 builds. So basically, what I'm picturing happened here is:

  • We pushed 1.18 to the general population
  • 5 days later, the Store determined the Terminal needed to be updated one way or another
  • The Store injected a thread into the terminal
  • the Terminal hung / crashed
  • now that the Terminal wasn't running, the Store took the opportunity to update the Terminal.

Feel free to send me the password to the dump though. Should be easy enough to ID from the stack.

@zadjii-msft commented on GitHub (Oct 24, 2023): Oh, no the Windows Store will literally inject a thread into an app to kill it to install an update for that app if it wasn't ever closed within some window after an update is available. The manifest entry to prevent that behavior only got added in the _latest_ Windows 11 builds. So basically, what I'm picturing happened here is: * We pushed 1.18 to the general population * 5 days later, the Store determined the Terminal needed to be updated one way or another * The Store injected a thread into the terminal * the Terminal hung / crashed * now that the Terminal wasn't running, the Store took the opportunity to update the Terminal. Feel free to send me the password to the dump though. Should be easy enough to ID from the stack.
claunia commented 2026-01-31 07:22:21 +00:00
Author
Owner
Copy Link

@mailinglists35 commented on GitHub (Oct 25, 2023):

thanks for the explanation, password sent to microsoft email. however,
I have Store configured to not Auto update apps - in Store - settings, the toggle to auto update is disabled.

@mailinglists35 commented on GitHub (Oct 25, 2023): thanks for the explanation, password sent to microsoft email. however, I have Store configured to **not** Auto update apps - in Store - settings, the toggle to auto update is disabled.
claunia commented 2026-01-31 07:22:21 +00:00
Author
Owner
Copy Link

@mailinglists35 commented on GitHub (Nov 12, 2023):

hi @zadjii-msft, were you able to download the memory dump files? I've emailed the nextcloud link password to your @ microsoft email

@mailinglists35 commented on GitHub (Nov 12, 2023): hi @zadjii-msft, were you able to download the memory dump files? I've emailed the nextcloud link password to your @ microsoft email
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 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#20726
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?