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

Multi-line emoji crashes program #5235

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

Originally created by @VikingScientist on GitHub (Nov 27, 2019).

Environment

Windows build number: 10.0.18362 Build 18362
Windows Terminal version (if applicable):  0.7.3291.0


Any other software?

Steps to reproduce

Open a new WSL terminal and fill a commandline with emojis (i.e. copy-paste from https://getemoji.com/ ). Resize the terminal window (width) so emojis would need to change line, i.e. the newline character would move location.

Expected behavior

Program would not crash

Actual behavior

Program crashes. "WindowsTerminal.exe is not responding, would you like to close the program".

NOTE: It does not appear with all emojis, but the string " 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳" does cause a crash

Originally created by @VikingScientist on GitHub (Nov 27, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- 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. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.18362 Build 18362 Windows Terminal version (if applicable): 0.7.3291.0 Any other software? ``` # Steps to reproduce Open a new WSL terminal and fill a commandline with emojis (i.e. copy-paste from https://getemoji.com/ ). Resize the terminal window (width) so emojis would need to change line, i.e. the newline character would move location. # Expected behavior Program would not crash # Actual behavior Program crashes. "WindowsTerminal.exe is not responding, would you like to close the program". NOTE: It does not appear with all emojis, but the string " 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳 🤯 😬 😰 😱 🥵 🥶 😳" does cause a crash
claunia added the Resolution-DuplicateProduct-TerminalSeverity-Crash labels 2026-01-31 00:08:17 +00:00
claunia commented 2026-01-31 00:08:17 +00:00
Author
Owner
Copy Link

@0xd4d commented on GitHub (Nov 27, 2019):

Smaller repro, open WSL in WT, paste one of these lines

  • 🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶
  • 🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵
    "initialCols": 120,
    "initialRows": 30,
@0xd4d commented on GitHub (Nov 27, 2019): Smaller repro, open WSL in WT, paste one of these lines - 🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶 - 🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵🥵 ```json "initialCols": 120, "initialRows": 30, ```
claunia commented 2026-01-31 00:08:18 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 27, 2019):

I have a feeling that this is #1360, which will be solved by #780, but just to make sure it is in fact the same thing, could you file a crash report?

/feedback

@zadjii-msft commented on GitHub (Nov 27, 2019): I have a feeling that this is #1360, which will be solved by #780, but just to make sure it is in fact the same thing, could you file a crash report? /feedback
claunia commented 2026-01-31 00:08:18 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 27, 2019):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

image image

@ghost commented on GitHub (Nov 27, 2019): Hi there!<br><br>Can you please send us feedback with the Feedback Hub with this issue and 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/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-31 00:08:18 +00:00
Author
Owner
Copy Link

@VikingScientist commented on GitHub (Nov 27, 2019):

I am unsure on where to find the Feedback Hub and thought #3739 was the crash report. If I press the "Feedback" button inside Windows Terminal, then I get sent directly to the github issue page.

I do not build from source, so I don't know where any debug information gets logged/printed.

@VikingScientist commented on GitHub (Nov 27, 2019): I am unsure on where to find the Feedback Hub and thought #3739 was the crash report. If I press the "Feedback" button inside Windows Terminal, then I get sent directly to the github issue page. I do not build from source, so I don't know where any debug information gets logged/printed.
claunia commented 2026-01-31 00:08:18 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 27, 2019):

You need to use the "feedback hub" application:
image

If you file a problem using the Feedback hub, and tag it as Apps > Windows Terminal, then hit the "share my feedback" button, you'll get an aka.ms link that we can use to look up the stack trace of the crash on our end.

@zadjii-msft commented on GitHub (Nov 27, 2019): You need to use the "feedback hub" application: ![image](https://user-images.githubusercontent.com/18356694/69735171-e304dc80-10f5-11ea-9816-f6e3f9f9a96d.png) If you file a problem using the Feedback hub, and tag it as Apps > Windows Terminal, then hit the "share my feedback" button, you'll get an `aka.ms` link that we can use to look up the stack trace of the crash on our end.
claunia commented 2026-01-31 00:08:18 +00:00
Author
Owner
Copy Link

@VikingScientist commented on GitHub (Nov 28, 2019):

This app is blocked by company policy on my computer. I could see if I could try and recreate the entire setup on a different personal computer, but at this point I think it is easier if others try to recreate the bug as I don't think it should be too hard to reproduce.

@VikingScientist commented on GitHub (Nov 28, 2019): This app is blocked by company policy on my computer. I could see if I could try and recreate the entire setup on a different personal computer, but at this point I think it is easier if others try to recreate the bug as I don't think it should be too hard to reproduce.
claunia commented 2026-01-31 00:08:19 +00:00
Author
Owner
Copy Link

@ts252 commented on GitHub (Nov 28, 2019):

Having had similar problems and found my way here, I've reported this via the feedback hub. I don't know how to get an aka.ms link from it but I referenced this github issue in my feedback.

For me it's an "unresponsive" not a crash per se. The tab you paste into freezes immediately, but other tabs are fine until you re-select the frozen one.

@ts252 commented on GitHub (Nov 28, 2019): Having had similar problems and found my way here, I've reported this via the feedback hub. I don't know how to get an aka.ms link from it but I referenced this github issue in my feedback. For me it's an "unresponsive" not a crash per se. The tab you paste into freezes immediately, but other tabs are fine until you re-select the frozen one.
claunia commented 2026-01-31 00:08:19 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 30, 2019):

Got this under a debugger -- looks the same as /dup #1360

@DHowett-MSFT commented on GitHub (Nov 30, 2019): Got this under a debugger -- looks the same as /dup #1360
claunia commented 2026-01-31 00:08:19 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 30, 2019):

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!

@ghost commented on GitHub (Nov 30, 2019): 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!
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 Product-Terminal Resolution-Duplicate Severity-Crash
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#5235
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?