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

Program does not stop when windows terminal is closed. #18023

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

Originally created by @kotenok2000 on GitHub (Jul 24, 2022).

Windows Terminal version

1.14.1963.0

Windows build number

10.0.22000.795

Other Software

doecm 1.10
https://mklasson.com/factors/index.php
https://mklasson.com/doecm_110_win.zip

Steps to reproduce

Unpack doecm_110_win.zip
run run.bat
close windows terminal window
ecm.exe gets killed. Doecm process doesn't get killed and tries to spawn ecm.exe
each time doecm tries to spawn ecm.exe cmd.exe fails with 0xc0000142 error

Expected Behavior

No response

Actual Behavior

When i close windows terminal window ecm.exe gets killed, but doecm.exe process doesn't get killed and tries to spawn ecm.exe
each time doecm tries to spawn ecm.exe cmd.exe fails with 0xc0000142 error

Originally created by @kotenok2000 on GitHub (Jul 24, 2022). ### Windows Terminal version 1.14.1963.0 ### Windows build number 10.0.22000.795 ### Other Software doecm 1.10 https://mklasson.com/factors/index.php https://mklasson.com/doecm_110_win.zip ### Steps to reproduce Unpack doecm_110_win.zip run run.bat close windows terminal window ecm.exe gets killed. Doecm process doesn't get killed and tries to spawn ecm.exe each time doecm tries to spawn ecm.exe cmd.exe fails with 0xc0000142 error ### Expected Behavior _No response_ ### Actual Behavior When i close windows terminal window ecm.exe gets killed, but doecm.exe process doesn't get killed and tries to spawn ecm.exe each time doecm tries to spawn ecm.exe cmd.exe fails with 0xc0000142 error
claunia added the Issue-BugNeeds-Tag-FixProduct-TerminalArea-Remoting labels 2026-01-31 06:01:31 +00:00
claunia commented 2026-01-31 06:01:33 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 25, 2022):

Does this happen outside of Windows Terminal?

@DHowett commented on GitHub (Jul 25, 2022): Does this happen outside of Windows Terminal?
claunia commented 2026-01-31 06:01:33 +00:00
Author
Owner
Copy Link

@kotenok2000 commented on GitHub (Jul 25, 2022):

It doesn't happen when i run it in conhost

@kotenok2000 commented on GitHub (Jul 25, 2022): It doesn't happen when i run it in conhost
claunia commented 2026-01-31 06:01:33 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 26, 2022):

run.bat

start /B /LOW /WAIT doecm.exe %1 %2 %3 %4 %5 %6 %7 %8 %9

There's a int main( int argc, char ** argv ) { in the doecm.cc file, which makes me think this is a console subsystem application, not a windows subsystem one.

From the included README:

One quirk of the "start" program used to set priority in run.bat is that it
disables ctrl-c. Ctrl-break still works though.

start /?

Starts a separate window to run a specified program or command.

START ["title"] [/D path] [/I] [/MIN] [/MAX] [/SEPARATE | /SHARED]
      [/LOW | /NORMAL | /HIGH | /REALTIME | /ABOVENORMAL | /BELOWNORMAL]
      [/NODE <NUMA node>] [/AFFINITY <hex affinity mask>] [/WAIT] [/B]
      [/MACHINE <x86|amd64|arm|arm64>][command/program] [parameters]
...
    B           Start application without creating a new window. The
                application has ^C handling ignored. Unless the application
                enables ^C processing, ^Break is the only way to interrupt
                the application.

So, doecm.exe gets a copy of the current console handles, not a new set of handles.

Unfortunately, there's not a lot of other source there to go off of. Seems like the Terminal is closing out the console handle, but for whatever reason, doecm.exe doesn't have anything to check if the console handle is still open and close itself. So it goes on, tries to spawn an ecm.exe, and that can't inherit the console (because there is no console), and that throws the 0xc0000142. That's mostly conjecture, based off the little bit of source code included.

We may need the maintainer to hop in here to help ID what's going on...

@zadjii-msft commented on GitHub (Jul 26, 2022): `run.bat` ```bat start /B /LOW /WAIT doecm.exe %1 %2 %3 %4 %5 %6 %7 %8 %9 ``` There's a `int main( int argc, char ** argv ) {` in the doecm.cc file, which makes me think this is a console subsystem application, not a windows subsystem one. From the included README: > One quirk of the "start" program used to set priority in run.bat is that it > disables ctrl-c. Ctrl-break still works though. `start /?` ``` Starts a separate window to run a specified program or command. START ["title"] [/D path] [/I] [/MIN] [/MAX] [/SEPARATE | /SHARED] [/LOW | /NORMAL | /HIGH | /REALTIME | /ABOVENORMAL | /BELOWNORMAL] [/NODE <NUMA node>] [/AFFINITY <hex affinity mask>] [/WAIT] [/B] [/MACHINE <x86|amd64|arm|arm64>][command/program] [parameters] ... B Start application without creating a new window. The application has ^C handling ignored. Unless the application enables ^C processing, ^Break is the only way to interrupt the application. ``` So, doecm.exe gets a copy of the current console handles, not a new set of handles. Unfortunately, there's not a lot of other source there to go off of. Seems like the Terminal is closing out the console handle, but for whatever reason, doecm.exe doesn't have anything to check if the console handle is still open and close itself. So it goes on, tries to spawn an `ecm.exe`, and that can't inherit the console (because there is no console), and that throws the 0xc0000142. That's mostly conjecture, based off the little bit of source code included. We may need the maintainer to hop in here to help ID what's going on...
claunia commented 2026-01-31 06:01:33 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 30, 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 (Jul 30, 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 06:01:34 +00:00
Author
Owner
Copy Link

@kotenok2000 commented on GitHub (Jul 30, 2022):

Bump.
I think the bot is buggy. it says that the issue "Needs-Author-Feedback" but in actuality it "Needs-Attention"

@kotenok2000 commented on GitHub (Jul 30, 2022): Bump. I think the bot is buggy. it says that the issue "Needs-Author-Feedback" but in actuality it "Needs-Attention"
claunia commented 2026-01-31 06:01:34 +00:00
Author
Owner
Copy Link

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

You know, yea that's a bit of a bug. This: image triggered the bot's "we need the author's feedback" routine accidentally.

That being said, we still do need direct insight from the maintainer of doecm here. From what I can see of the source, I would expect closing the terminal (and thereby closing the console) to close this process. It kinda feels like something that needs to be reported to doecm.

I'll give the bot another week, but there's not much more we can investigate here...

@zadjii-msft commented on GitHub (Aug 10, 2022): You know, yea that's a bit of a bug. This: ![image](https://user-images.githubusercontent.com/18356694/184027476-265cfa6a-bc0b-4028-a50a-74925df24ece.png) triggered the bot's "we need the author's feedback" routine accidentally. That being said, we still do need direct insight from the maintainer of `doecm` here. From what I can see of the source, I would expect closing the terminal (and thereby closing the console) to close this process. It kinda feels like something that needs to be reported to doecm. I'll give the bot another week, but there's not much more we can investigate here...
claunia commented 2026-01-31 06:01:34 +00:00
Author
Owner
Copy Link

@kotenok2000 commented on GitHub (Aug 10, 2022):

why does conhost close the process, but windows terminal doesn't?

@kotenok2000 commented on GitHub (Aug 10, 2022): why does conhost close the process, but windows terminal doesn't?
claunia commented 2026-01-31 06:01:34 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Dec 13, 2022):

This was fixed by #14282. Thank you again for your report! It was quite helpful during later testing.

@lhecker commented on GitHub (Dec 13, 2022): This was fixed by #14282. Thank you again for your report! It was quite helpful during later testing.
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-Remoting 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#18023
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?