starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

DesktopWindowXamlSource memory usage - possible leak #15701

New Issue
Closed
opened 2026-01-31 04:45:57 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 04:45:57 +00:00
Owner
Copy Link

Originally created by @elsaco on GitHub (Oct 26, 2021).

Windows Terminal version (or Windows build number)

Windows Terminal Preview ver. 1.12.2931.0

Other Software

Windows 10

Steps to reproduce

  1. launch WT with one tab only
  2. observer memory usage in task manager
  3. using ctrl+- decrease font size to minimum allowed
  4. check memory usage, focus on DesktopWindowXamlSource reading

Expected Behavior

  1. no large memory increase

Actual Behavior

  1. memory usage for DesktopWindowXamlSource doubles
  2. for each additional tab the memory usage increases when using smallest fonts
  3. memory usage does not increase when using ctrl+= to enlarge fonts

Memory use at WT launch, single tab:
wt_mem_usage

Sample usage with one tab opened:
wt_mem_usage_small

Sample memory usage with two tabs opened:
wt_mem_usage_small_two_tabs

Originally created by @elsaco on GitHub (Oct 26, 2021). ### Windows Terminal version (or Windows build number) Windows Terminal Preview ver. 1.12.2931.0 ### Other Software Windows 10 ### Steps to reproduce 1. launch WT with one tab only 2. observer memory usage in task manager 3. using `ctrl+-` decrease font size to minimum allowed 4. check memory usage, focus on `DesktopWindowXamlSource` reading ### Expected Behavior 1. no large memory increase ### Actual Behavior 1. memory usage for `DesktopWindowXamlSource` doubles 2. for each additional tab the memory usage increases when using smallest fonts 3. memory usage does not increase when using `ctrl+=` to enlarge fonts Memory use at WT launch, single tab: ![wt_mem_usage](https://user-images.githubusercontent.com/3933920/138933471-8b6b2900-5e2c-4a3c-a48a-a4919229c161.PNG) Sample usage with one tab opened: ![wt_mem_usage_small](https://user-images.githubusercontent.com/3933920/138933296-f9425134-d043-4f7b-a36f-6d0c1543addb.PNG) Sample memory usage with two tabs opened: ![wt_mem_usage_small_two_tabs](https://user-images.githubusercontent.com/3933920/138933369-ad5a91cf-ed67-4a35-86d6-432b44dfdf4c.png)
claunia added the Issue-QuestionNeeds-TriageNeeds-Tag-FixResolution-Answered labels 2026-01-31 04:45:58 +00:00
claunia commented 2026-01-31 04:45:59 +00:00
Author
Owner
Copy Link

@LuanVSO commented on GitHub (Oct 26, 2021):

when you decrease the size of the font you are making the size of the text buffer bigger, you can see the if you put the font size back to normal the memory usage is reduced. same thing with tabs, by creating tabs terminal needs to create a buffer to hold the text from that tab, if you close the tab, the memory will go down no leak.
"DesktopWindowXamlSource" is the main windows terminal executable you can see it if you enable the "command line" column in task manager:
image

@LuanVSO commented on GitHub (Oct 26, 2021): when you decrease the size of the font you are making the size of the text buffer bigger, you can see the if you put the font size back to normal the memory usage is reduced. same thing with tabs, by creating tabs terminal needs to create a buffer to hold the text from that tab, if you close the tab, the memory will go down no leak. "DesktopWindowXamlSource" is the main windows terminal executable you can see it if you enable the "command line" column in task manager: ![image](https://user-images.githubusercontent.com/43626415/138941788-11f7a4a5-1abf-48cc-9aeb-484b87d87656.png)
claunia commented 2026-01-31 04:45:59 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 26, 2021):

Yep, I don't think I have anything else to add here. That answer seems to cover it all ☺️

@zadjii-msft commented on GitHub (Oct 26, 2021): Yep, I don't think I have anything else to add here. That answer seems to cover it all ☺️
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-Question Needs-Tag-Fix Needs-Triage Resolution-Answered
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#15701
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?