starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 07:54:35 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Mouse click on terminal window make it instantly crash #23740

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

Originally created by @jarredou on GitHub (Oct 20, 2025).

Windows Terminal version

latest

Windows build number

No response

Other Software

No response

Steps to reproduce

open terminal, click somewhere

Expected Behavior

no instant crash

Actual Behavior

instant crash

Originally created by @jarredou on GitHub (Oct 20, 2025). ### Windows Terminal version latest ### Windows build number _No response_ ### Other Software _No response_ ### Steps to reproduce open terminal, click somewhere ### Expected Behavior no instant crash ### Actual Behavior instant crash
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:51:06 +00:00
claunia commented 2026-01-31 08:51:08 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 20, 2025):

"Latest" isn't a terminal version. You could be on canary, on preview, stable, on a version that hasn't gotten updated by the Store yet, in an insider selfhost channel, or even on a dev build.

Can you share the output of wt -v/?

@zadjii-msft commented on GitHub (Oct 20, 2025): "Latest" isn't a terminal version. You could be on canary, on preview, stable, on a version that hasn't gotten updated by the Store yet, in an insider selfhost channel, or even on a dev build. Can you share the output of `wt -v`/?
claunia commented 2026-01-31 08:51:08 +00:00
Author
Owner
Copy Link

@jarredou commented on GitHub (Oct 20, 2025):

"latest"

Image
@jarredou commented on GitHub (Oct 20, 2025): "latest" <img width="416" height="157" alt="Image" src="https://github.com/user-attachments/assets/3683f58c-f374-4369-a6b9-211ed1bf4148" />
claunia commented 2026-01-31 08:51:08 +00:00
Author
Owner
Copy Link

@jarredou commented on GitHub (Oct 20, 2025):

More serioulsy, it has happened again, while the terminal window was training an ML model, terminal window was bacground, I've clicked on it to make it focused, and it died instantly. Ongoing training = RIP.

@jarredou commented on GitHub (Oct 20, 2025): More serioulsy, it has happened again, while the terminal window was training an ML model, terminal window was bacground, I've clicked on it to make it focused, and it died instantly. Ongoing training = RIP.
claunia commented 2026-01-31 08:51:08 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 20, 2025):

We're sorry that it crashed. As you're surely aware though, we can't do anything with just "instant crash" as the only information.

If you otherwise have not collected crash dumps yet, you can find steps here to activate automatic crash dump collection: https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically

Edit: Please note that if your system goes completely OOM during training, the terminal may crash.

@lhecker commented on GitHub (Oct 20, 2025): We're sorry that it crashed. As you're surely aware though, we can't do anything with just "instant crash" as the only information. If you otherwise have not collected crash dumps yet, you can find steps here to activate automatic crash dump collection: https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically Edit: Please note that if your system goes completely OOM during training, the terminal may crash.
claunia commented 2026-01-31 08:51:09 +00:00
Author
Owner
Copy Link

@jarredou commented on GitHub (Oct 21, 2025):

Please note that I will not use your terminal anymore

@jarredou commented on GitHub (Oct 21, 2025): Please note that I will not use your terminal anymore
claunia commented 2026-01-31 08:51:09 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 21, 2025):

Unfortunately, we cannot fix your bug if you do not report it with actionable information. I'm sorry.

@DHowett commented on GitHub (Oct 21, 2025): Unfortunately, we cannot fix your bug if you do not report it with actionable information. I'm sorry.
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-Triage
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#23740
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?