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

Slow memory leak in Windows Terminal #19107

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

Originally created by @Treit on GitHub (Dec 21, 2022).

Originally assigned to: @lhecker on GitHub.

Windows Terminal version

1.16.3464.0

Windows build number

10.0.25272.0

Other Software

There appears to be a slow memory leak in Windows Terminal.

I was running my small Terminal Stress app that I have used to find other bugs in the past. I accidentally left it running overnight and when I came in the next morning I found WindowsTerminal was consuming a large amount of memory.

This appears to be reproducible by simply running the Terminal Stress app (a simple .NET console application) and letting it run.

Steps to reproduce

  1. Build Terminal Stress and run it from a terminal window.

  2. Let it run for a long time.

  3. Observe that the memory usage for Windows Terminal climbs slowly.

  4. Eventually stop the program from running.

  5. Note that the memory usage (commit size) remains high.

Expected Behavior

Memory usage should remain relatively flat as the test program simply prints random characters to random positions on the screen.

Actual Behavior

The memory increases, quite slowly but surely.

In my most recent case I found the memory usage was more than 3GB after the stress program had run for about 20 hours.

Originally created by @Treit on GitHub (Dec 21, 2022). Originally assigned to: @lhecker on GitHub. ### Windows Terminal version 1.16.3464.0 ### Windows build number 10.0.25272.0 ### Other Software There appears to be a slow memory leak in Windows Terminal. I was running my small [Terminal Stress](https://github.com/Treit/TerminalStress) app that I have used to find other bugs in the past. I accidentally left it running overnight and when I came in the next morning I found WindowsTerminal was consuming a large amount of memory. This appears to be reproducible by simply running the Terminal Stress app (a simple .NET console application) and letting it run. ### Steps to reproduce 1. Build [Terminal Stress](https://github.com/Treit/TerminalStress) and run it from a terminal window. 2. Let it run for a long time. 3. Observe that the memory usage for Windows Terminal climbs slowly. 4. Eventually stop the program from running. 5. Note that the memory usage (commit size) remains high. ### Expected Behavior Memory usage should remain relatively flat as the test program simply prints random characters to random positions on the screen. ### Actual Behavior The memory increases, quite slowly but surely. In my most recent case I found the memory usage was more than 3GB after the stress program had run for about 20 hours.
claunia added the Area-OutputIssue-BugNeeds-Tag-FixProduct-Terminal labels 2026-01-31 06:34:00 +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 Area-Output 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#19107
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?