CTRL+C does not kill windows terminal and stuck! #9444

Closed
opened 2026-01-31 01:54:36 +00:00 by claunia · 4 comments
Owner

Originally created by @thisVioletHydra on GitHub (Jul 5, 2020).

Environment

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.19041.0 Microsoft Windows NT 10.0.19041.0
Windows Terminal     1.0.1811.0

I am running a local server on nuxtjs
I can’t complete stop the process, I press ctrl + c and the terminal freezes to turn it off, I need to close it with a cross
image

Originally created by @thisVioletHydra on GitHub (Jul 5, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 ```code Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0 Windows Terminal 1.0.1811.0 ``` I am running a local server on nuxtjs I can’t complete stop the process, I press ctrl + c and the terminal freezes to turn it off, I need to close it with a cross ![image](https://user-images.githubusercontent.com/11839238/86539922-2e436100-bf09-11ea-89f1-0b97332f8fee.png)
claunia added the Resolution-Duplicate label 2026-01-31 01:54:36 +00:00
Author
Owner

@KalleOlaviNiemitalo commented on GitHub (Jul 5, 2020):

3221225786 = 0xC000013A = STATUS_CONTROL_C_EXIT

It looks like the process has exited, but because the exit code is not zero, Windows Terminal has left the tab open so you can see what happened. See How the profile closes when exiting and https://github.com/microsoft/terminal/issues/5214 for how to configure this.

@KalleOlaviNiemitalo commented on GitHub (Jul 5, 2020): 3221225786 = 0xC000013A = STATUS_CONTROL_C_EXIT It looks like the process has exited, but because the exit code is not zero, Windows Terminal has left the tab open so you can see what happened. See [How the profile closes when exiting](https://docs.microsoft.com/windows/terminal/customize-settings/profile-settings#how-the-profile-closes-when-exiting) and <https://github.com/microsoft/terminal/issues/5214> for how to configure this.
Author
Owner

@DHowett commented on GitHub (Jul 6, 2020):

Yes, this is operating as designed. Your process was terminated at your request and it has exited with a code indicating that it "failed." Failing codes, by default, cause the tab to remain open. /dup #5214

@DHowett commented on GitHub (Jul 6, 2020): Yes, this is operating as designed. Your process was terminated _at your request_ and it has exited with a code indicating that it "failed." Failing codes, by default, cause the tab to remain open. /dup #5214
Author
Owner

@ghost commented on GitHub (Jul 6, 2020):

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 (Jul 6, 2020): 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!
Author
Owner

@thisVioletHydra commented on GitHub (Jul 7, 2020):

Set: "closeOnExit": "always" helped me thx

@thisVioletHydra commented on GitHub (Jul 7, 2020): Set: `"closeOnExit": "always"` helped me thx
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#9444