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

process exited with code 15 #23439

New Issue
Open
opened 2026-01-31 08:42:13 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 08:42:13 +00:00
Owner
Copy Link

Originally created by @morisono on GitHub (Jul 13, 2025).

Windows Terminal version

1.22.11141.0

Windows build number

10.0.26100.0

Other Software

Image

Description

While using VS Code (and other apps), the following message appears, and both VS Code and the Terminal forcefully close:

[process exited with code 15 (0x0000000f)] You can now close this terminal with Ctrl+D, or press Enter to restart.

This is extremely disruptive. Any insights or shared experiences would be appreciated.

What I've Tried

  • Opened Event Viewer (eventvwr.msc) and reviewed logs
  • Searched ChatGPT / StackOverflow / Microsoft forums

Observations / Error Message

From Event Viewer:

A new BITS job could not be created. The current job count for the user WIN11\xxx (60) is equal to or greater than the job limit (60) specified through group policy. To correct the problem, complete or cancel the BITS jobs that haven't made progress by looking at the error, and restart the BITS service. If this error recurs, contact your system administrator and increase the per-user and per-computer Group Policy job limits.

However, AI tools claim this BITS issue is unrelated to the process exit problem.

Possible Next Steps

  • Investigate whether low memory or disk space in WSL2 is causing this—adjust configuration via wsl.conf.
  • Check if the BITS job limit (60) is actually causing the issue and how to raise it.

Environment

OS: Ubuntu noble 24.04 x86_64  
Host: Windows Subsystem for Linux – Ubuntu‑24.04 (WSL2, build 2.5.9.0)  
Kernel: Linux 6.6.87.2‑microsoft‑standard‑WSL2  
Uptime: ~10 min  
Shell: fish 3.7.0  
WM: WSLg (Wayland)  
Terminal: Windows Terminal  
CPU: AMD Ryzen 9 3950X  
Memory: ~7.76 GiB (only 662 MiB free)  
Swap: Disabled  
Storage:  
  - `/`: 282 GiB / 1 TiB (28%)  
  - `/mnt/c`: 1.8 TiB / 1.82 TiB (99%) full  
  - Other drives nearing capacity  
Network: WSL eth0 – 10.2.0.2/32  
Locale: en_US.UTF‑8

References

Request

If you have any relevant information—e.g. similar experiences, causes, or solutions—please share it. This issue is critical and urgent for me.

Let me know if you'd like me to tweak formatting or add more context!

Steps to reproduce

  • High memory pressure may triggers exit code 15?

  • WSL2 uses a lightweight VM and allocates RAM dynamically—exhaustion can abruptly kill terminal processes

  • Exit code 15 is SIGTERM, hinting at a forced termination (likely by OOM or WSL system)

  • WSL memory usage was already high (~92% used) and swap disabled

  • Reproduce with stress-ng:

    sudo apt update && sudo apt install stress-ng
stress-ng --vm 2 --vm-keep --vm-bytes 90% --timeout 60s

  • Then run any interactive command in VS Code or terminal and see if it exits with code 15

Expected Behavior

No response

Actual Behavior

Both Windows Terminal and VS Code's integrated terminal abruptly closes simultaneously.

Originally created by @morisono on GitHub (Jul 13, 2025). ### Windows Terminal version 1.22.11141.0 ### Windows build number 10.0.26100.0 ### Other Software <img width="947" height="245" alt="Image" src="https://github.com/user-attachments/assets/44137290-9cb5-4349-b2c1-18caa916ce25" /> ### Description While using VS Code (and other apps), the following message appears, and both VS Code and the Terminal forcefully close: ``` [process exited with code 15 (0x0000000f)] You can now close this terminal with Ctrl+D, or press Enter to restart. ``` This is extremely disruptive. Any insights or shared experiences would be appreciated. ### What I've Tried * Opened **Event Viewer** (`eventvwr.msc`) and reviewed logs * Searched ChatGPT / StackOverflow / Microsoft forums ### Observations / Error Message From Event Viewer: ``` A new BITS job could not be created. The current job count for the user WIN11\xxx (60) is equal to or greater than the job limit (60) specified through group policy. To correct the problem, complete or cancel the BITS jobs that haven't made progress by looking at the error, and restart the BITS service. If this error recurs, contact your system administrator and increase the per-user and per-computer Group Policy job limits. ``` However, AI tools claim this BITS issue is unrelated to the process exit problem. ### Possible Next Steps * Investigate whether low memory or disk space in WSL2 is causing this—adjust configuration via `wsl.conf`. * Check if the BITS **job limit (60)** is actually causing the issue and how to raise it. ### Environment ``` OS: Ubuntu noble 24.04 x86_64 Host: Windows Subsystem for Linux – Ubuntu‑24.04 (WSL2, build 2.5.9.0) Kernel: Linux 6.6.87.2‑microsoft‑standard‑WSL2 Uptime: ~10 min Shell: fish 3.7.0 WM: WSLg (Wayland) Terminal: Windows Terminal CPU: AMD Ryzen 9 3950X Memory: ~7.76 GiB (only 662 MiB free) Swap: Disabled Storage: - `/`: 282 GiB / 1 TiB (28%) - `/mnt/c`: 1.8 TiB / 1.82 TiB (99%) full - Other drives nearing capacity Network: WSL eth0 – 10.2.0.2/32 Locale: en_US.UTF‑8 ``` ### References * [Windows system error codes (0–499)](https://learn.microsoft.com/en-us/windows/win32/debug/system-error-codes--0-499-) * [VS Code / Windows Terminal issue #16363 on GitHub- ](https://github.com/microsoft/terminal/issues/16363) * [ChatGPT thread: 68730c12-efb0-8009-92cc-08fe0a7499b5](https://chatgpt.com/share/68730c12-efb0-8009-92cc-08fe0a7499b5) ### Request If you have any relevant information—e.g. similar experiences, causes, or solutions—please share it. This issue is critical and urgent for me. Let me know if you'd like me to tweak formatting or add more context! ### Steps to reproduce - High memory pressure may triggers exit code 15? * WSL2 uses a lightweight VM and allocates RAM dynamically—exhaustion can abruptly kill terminal processes * Exit code 15 is `SIGTERM`, hinting at a forced termination (likely by OOM or WSL system) * WSL memory usage was already high (\~92% used) and swap disabled * Reproduce with `stress-ng`: ```bash sudo apt update && sudo apt install stress-ng stress-ng --vm 2 --vm-keep --vm-bytes 90% --timeout 60s ``` * Then run any interactive command in VS Code or terminal and see if it exits with code 15 ### Expected Behavior _No response_ ### Actual Behavior Both **Windows Terminal** and **VS Code's integrated terminal** abruptly closes simultaneously.
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:42:14 +00:00
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#23439
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?