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 pasting text #17670

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

Originally created by @ilor on GitHub (Jun 10, 2022).

Windows Terminal version

1.14.1451.0

Windows build number

10.0.19044.1706

Other Software

No response

Steps to reproduce

Pasted a multi-line text into the terminal (nothing excessive, 5 lines 144 chars each, ascii)

Expected Behavior

No response

Actual Behavior

Crashed all tabs with no error message. The multi-line paste warning did not appear (it was a multi-line paste).

I can't reliably reproduce the issue (pasting the exact same text worked OK on a retry). I get that this is not very actionable, but that's all I have at the moment. If there's some crash dump path I can look into, or settings to make future crashes dump some info, I'd appreciate hints.

Originally created by @ilor on GitHub (Jun 10, 2022). ### Windows Terminal version 1.14.1451.0 ### Windows build number 10.0.19044.1706 ### Other Software _No response_ ### Steps to reproduce Pasted a multi-line text into the terminal (nothing excessive, 5 lines 144 chars each, ascii) ### Expected Behavior _No response_ ### Actual Behavior Crashed all tabs with no error message. The multi-line paste warning did not appear (it was a multi-line paste). I can't reliably reproduce the issue (pasting the exact same text worked OK on a retry). I get that this is not very actionable, but that's all I have at the moment. If there's some crash dump path I can look into, or settings to make future crashes dump some info, I'd appreciate hints.
claunia commented 2026-01-31 05:49:41 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 10, 2022):

Can you try following the steps in this post to set up automatic crash dumps/? (For more info, see this link) If that works, then you should be able to automatically get a .dmp of the terminal when it crashes. Then, can you zip that dump up and send it to us, so we can investigate? Thanks!

@zadjii-msft commented on GitHub (Jun 10, 2022): Can you try following the steps in [this post](https://www.meziantou.net/tip-automatically-create-a-crash-dump-file-on-error.htm) to set up automatic crash dumps/? (For more info, see [this link](https://docs.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps)) If that works, then you should be able to automatically get a `.dmp` of the terminal when it crashes. Then, can you zip that dump up and send it to us, so we can investigate? Thanks!
claunia commented 2026-01-31 05:49:41 +00:00
Author
Owner
Copy Link

@ilor commented on GitHub (Jun 10, 2022):

I definitely will, thanks!

@ilor commented on GitHub (Jun 10, 2022): I definitely will, thanks!
claunia commented 2026-01-31 05:49:41 +00:00
Author
Owner
Copy Link

@ilor commented on GitHub (Jun 10, 2022):

Interesting, I must've followed that exact guide some time in the past and long since forgotten about it -- but it seems I had this active, and I do have a WindowsTerminal.exe dump. It seems to correspond, modification-time-wise, to when I had the crash.

The file is 17MB, 2Mb compressed. Should I just attach it here?

@ilor commented on GitHub (Jun 10, 2022): Interesting, I must've followed that exact guide some time in the past and long since forgotten about it -- but it seems I had this active, and I do have a WindowsTerminal.exe dump. It seems to correspond, modification-time-wise, to when I had the crash. The file is 17MB, 2Mb compressed. Should I just attach it here?
claunia commented 2026-01-31 05:49:42 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jun 10, 2022):

@ilor Such dumps can contain private data (like usernames and other bits of information).
Could you send the dump via mail to <my github username>@microsoft.com? I'll then forward it to the rest of the team. 🙂
(An informal mail is absolutely fine.)

@lhecker commented on GitHub (Jun 10, 2022): @ilor Such dumps can contain private data (like usernames and other bits of information). Could you send the dump via mail to `<my github username>@microsoft.com`? I'll then forward it to the rest of the team. 🙂 (An informal mail is absolutely fine.)
claunia commented 2026-01-31 05:49:42 +00:00
Author
Owner
Copy Link

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

tl;dr:

  • It's an unhandled error in Windows_UI_Xaml!DirectUI::ErrorHelper::ProcessUnhandledError
  • The HRESULT m_ErrorCode passed to that function is 0x80004005 (Unspecified error)
  • The m_description string for the error has been stripped from the MiniDump 😿
  • Failure bucket – no hits: a14d2eeb-64f1-cf9a-221e-7e98eff63046

Maybe there's a !xamlstowed exception in there, but it sounds like the dump unfortunately didn't have anything useful to work with. If you can get a reliable repro at all, then trying to repro this with a Feedback Hub recording might be useful. That sometimes catches extra information. (The bot is about to recommend the Terminal area path in feedback hub, but I might recommend
image
instead)

/feedback

@zadjii-msft commented on GitHub (Jun 13, 2022): > tl;dr: > * It's an unhandled error in `Windows_UI_Xaml!DirectUI::ErrorHelper::ProcessUnhandledError` > * The `HRESULT m_ErrorCode` passed to that function is 0x80004005 (Unspecified error) > * The `m_description` string for the error has been stripped from the MiniDump 😿 > * Failure bucket – no hits: `a14d2eeb-64f1-cf9a-221e-7e98eff63046` Maybe there's a `!xamlstowed` exception in there, but it sounds like the dump unfortunately didn't have anything useful to work with. If you can get a reliable repro at all, then trying to repro this with a Feedback Hub recording might be useful. That sometimes catches extra information. (The bot is about to recommend the Terminal area path in feedback hub, but I might recommend ![image](https://user-images.githubusercontent.com/18356694/173402511-1534089d-07e8-41f4-b25d-75e3e5f1ce4c.png) instead) /feedback
claunia commented 2026-01-31 05:49:42 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 13, 2022):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?

Thanks!

image

image

image

@ghost commented on GitHub (Jun 13, 2022): Hi there!<br><br>Can you please send us feedback with the [Feedback Hub](https://support.microsoft.com/en-us/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332) with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, 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/18356694/140811502-a068f78b-89d2-4587-925a-73e19652b830.png)<br><br>![image](https://user-images.githubusercontent.com/18356694/140811557-cdc22a0f-fa6a-4f6a-953e-73b51f5548a3.png)<br><br>![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-31 05:49:42 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 17, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jun 17, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 05:49:42 +00:00
Author
Owner
Copy Link

@ilor commented on GitHub (Jun 17, 2022):

Unfortunately I haven't seen this issue since, it only happened that one time.

@ilor commented on GitHub (Jun 17, 2022): Unfortunately I haven't seen this issue since, it only happened that one time.
claunia commented 2026-01-31 05:49:43 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 20, 2022):

I'm gonna close this as an intermittent failure. If you start seeing this regularly again, let us know and we can reopen and investigate more. Thanks!

@zadjii-msft commented on GitHub (Jun 20, 2022): I'm gonna close this as an intermittent failure. If you start seeing this regularly again, let us know and we can reopen and investigate more. 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 Issue-Bug Needs-Attention Needs-Tag-Fix Needs-Triage Resolution-No-Repro
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#17670
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?