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

Canary: [regression] Trouble work in headless mode #22820

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

Originally created by @Zeroes1 on GitHub (Jan 29, 2025).

Originally assigned to: @lhecker on GitHub.

Windows Terminal version

1.23.10282.0

Windows build number

10.0.19045.5371

Other Software

No response

Steps to reproduce

set WT work in background mode it's turn ON with settings.json with option:
"compatibility.allowHeadless": true,

Expected Behavior

under version
terminal-1.23.3101.0
..
terminal-1.23.3461.0

start WT
close WT by method:
a) click mouse on cross window (or press alt-f4)
b) use hotkey for close panel - ctrl-shift-w

after this in process exist only:
WindowsTerminal.exe

Actual Behavior

under version
terminal-1.23.3481.0
..
terminal-1.23.10282.0

after close panel in process exist:
WindowsTerminal.exe
and child process:
OpenConsole.exe

(if use default profile for run PowerShell)

if use profile for run Far Manager
after close WT in process exist:
WindowsTerminal.exe
and child process:
OpenConsole.exe
Far.exe

if 10 times start WT and 10 time close panel
we get:
one process WindowsTerminal.exe
10 process OpenConsole.exe
10 process Far.exe

Originally created by @Zeroes1 on GitHub (Jan 29, 2025). Originally assigned to: @lhecker on GitHub. ### Windows Terminal version 1.23.10282.0 ### Windows build number 10.0.19045.5371 ### Other Software _No response_ ### Steps to reproduce set WT work in background mode it's turn ON with settings.json with option: "compatibility.allowHeadless": true, ### Expected Behavior under version terminal-1.23.3101.0 .. terminal-1.23.3461.0 start WT close WT by method: a) click mouse on cross window (or press alt-f4) b) use hotkey for close panel - ctrl-shift-w after this in process exist only: WindowsTerminal.exe ### Actual Behavior under version terminal-1.23.3481.0 .. terminal-1.23.10282.0 after close panel in process exist: WindowsTerminal.exe and child process: OpenConsole.exe (if use default profile for run PowerShell) if use profile for run Far Manager after close WT in process exist: WindowsTerminal.exe and child process: OpenConsole.exe Far.exe if 10 times start WT and 10 time close panel we get: one process WindowsTerminal.exe 10 process OpenConsole.exe 10 process Far.exe
claunia added the Issue-BugNeeds-Tag-FixProduct-TerminalArea-Windowing labels 2026-01-31 08:24:26 +00:00
claunia commented 2026-01-31 08:24:28 +00:00
Author
Owner
Copy Link

@Zeroes1 commented on GitHub (Feb 2, 2025):

Additional information:

  1. If try close last window WT with internal command: ( exit [+ enter] for powershell/cmd, F10 for Far Manager)
    the associated processes [OpenConsole.exe + powershell.exe/cmd.exe/Far.exe] will be closed normally.

  2. when close last window WT (with ANY method)
    process WindowsTerminal.exe (headlesses) start showing the application icon on the taskbar (in terminal-1.23.3461.0 or earlier without this effect)

Image

@Zeroes1 commented on GitHub (Feb 2, 2025): Additional information: 1) If try close last window WT with internal command: ( exit [+ enter] for powershell/cmd, F10 for Far Manager) the associated processes [OpenConsole.exe + powershell.exe/cmd.exe/Far.exe] will be closed normally. 2) when close last window WT (with ANY method) process WindowsTerminal.exe (headlesses) start showing the application icon on the taskbar (in terminal-1.23.3461.0 or earlier without this effect) ![Image](https://github.com/user-attachments/assets/ee07b5be-09c9-4556-a18f-4fc5de75f35a)
claunia commented 2026-01-31 08:24:28 +00:00
Author
Owner
Copy Link

@Zeroes1 commented on GitHub (Feb 21, 2025):

@lhecker any idea? [pls check also #18497]

@Zeroes1 commented on GitHub (Feb 21, 2025): @lhecker any idea? [pls check also #18497]
claunia commented 2026-01-31 08:24:29 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Feb 21, 2025):

I haven't worked on this yet because I'm working on another project internally right now. I have promised though to fix the bugs I caused sometime soon, maybe next week. :)

@lhecker commented on GitHub (Feb 21, 2025): I haven't worked on this yet because I'm working on another project internally right now. I have promised though to fix the bugs I caused sometime soon, maybe next week. :)
claunia commented 2026-01-31 08:24:29 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Feb 24, 2025):

I cannot reproduce this issue. I tried:

  • Enable headless mode
  • Open the first window with 1 tab
  • Ctrl+Shift+W
  • --> No processes leaked

What did I do wrong?

The good news is that I did find another bug thanks to you which I'll fix soon.

@lhecker commented on GitHub (Feb 24, 2025): I cannot reproduce this issue. I tried: * Enable headless mode * Open the first window with 1 tab * Ctrl+Shift+W * --> No processes leaked What did I do wrong? The good news is that I did find another bug thanks to you which I'll fix soon.
claunia commented 2026-01-31 08:24:29 +00:00
Author
Owner
Copy Link

@Zeroes1 commented on GitHub (Feb 26, 2025):

@lhecker what you version check?

latest canary terminal-1.24.551.0 already without this problem (issue 18497 gone too)
terminal-1.24.531.0 - latest with problem (from 22 feb)

@Zeroes1 commented on GitHub (Feb 26, 2025): @lhecker what you version check? latest canary terminal-1.24.551.0 already **without** this problem (issue 18497 gone too) terminal-1.24.531.0 - latest with problem (from 22 feb)
claunia commented 2026-01-31 08:24:30 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Feb 26, 2025):

Oh, so the issue is gone now? Did I understand you correctly? Let me know if I got it wrong. 🙂
In that case it was probably fixed by #18621. Thank you for the report!

@lhecker commented on GitHub (Feb 26, 2025): Oh, so the issue is gone now? Did I understand you correctly? Let me know if I got it wrong. 🙂 In that case it was probably fixed by #18621. Thank you for the 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 Area-Windowing Issue-Bug Needs-Tag-Fix Product-Terminal
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#22820
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?