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

Enormous page file usage #17126

New Issue
Closed
opened 2026-01-31 05:32:51 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 05:32:51 +00:00
Owner
Copy Link

Originally created by @Forinil on GitHub (Mar 30, 2022).

Windows Terminal version

1.11.3471.0 and 1.13.10733.0

Windows build number

10.0.19044.0

Other Software

PowerShell 7.2.2
Gradle 6.4.1

Steps to reproduce

I'm using Windows Terminal at work to open several tabs, one of which is always a PowerShell tab in which I run my Gradle builds.

Two days ago I run out of SSD space and checked if I had any huge files on the drive. To my suprise pagefile.sys was over 20 GB in size and when I checked the Resource Monitor, it showed that Windows Terminal has committed over 16 GB of memory.

The next day I used the Resource Monitor to monitor the Terminal's committed memory and it seems every build added several GB.

I installed the Terminal Preview and used it - instead of the stable version - the day after that to see if it has the same problem. It has.

Expected Behavior

A reasonable amount of committed memory used. Committed memory released after a while - when it's presumably no longer needed.

Actual Behavior

A huge amount of commit memory (measured in GB) used. Several GB added with every build. No - or virtually no - committed memory ever released.

Originally created by @Forinil on GitHub (Mar 30, 2022). ### Windows Terminal version 1.11.3471.0 and 1.13.10733.0 ### Windows build number 10.0.19044.0 ### Other Software PowerShell 7.2.2 Gradle 6.4.1 ### Steps to reproduce I'm using Windows Terminal at work to open several tabs, one of which is always a PowerShell tab in which I run my Gradle builds. Two days ago I run out of SSD space and checked if I had any huge files on the drive. To my suprise _pagefile.sys_ was over 20 GB in size and when I checked the Resource Monitor, it showed that Windows Terminal has committed over 16 GB of memory. The next day I used the Resource Monitor to monitor the Terminal's committed memory and it seems every build added several GB. I installed the Terminal Preview and used it - instead of the stable version - the day after that to see if it has the same problem. It has. ### Expected Behavior A reasonable amount of committed memory used. Committed memory released after a while - when it's presumably no longer needed. ### Actual Behavior A huge amount of commit memory (measured in GB) used. Several GB added with every build. No - or virtually no - committed memory ever released.
claunia commented 2026-01-31 05:32:52 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 13, 2022):

This seems impossibly bad - Like, I don't know how we'd possibly commit that much memory before just hitting an out of memory error.

Is the committed memory attributed to windowsterminal.exe, or is it possible there's some other process in the tree that's holding that memory?

I know we have a guide somewhere for debugging what's actually allocating memory. Lemme see if I can dig it up.

@zadjii-msft commented on GitHub (Apr 13, 2022): This seems impossibly bad - Like, I don't know how we'd possibly commit that much memory before just hitting an out of memory error. Is the committed memory attributed to `windowsterminal.exe`, or is it possible there's some other process in the tree that's holding that memory? I know we have a guide somewhere for debugging what's actually allocating memory. Lemme see if I can dig it up.
claunia commented 2026-01-31 05:32:53 +00:00
Author
Owner
Copy Link

@Forinil commented on GitHub (Apr 13, 2022):

All I can tell you at the moment is that if I use ConEmu instead of Windows Terminal, leaving everything else the same, I don't see any processes that use that amount of memory.

Let me know if there's anything more I can do.

@Forinil commented on GitHub (Apr 13, 2022): All I can tell you at the moment is that if I use ConEmu instead of Windows Terminal, leaving everything else the same, I don't see any processes that use that amount of memory. Let me know if there's anything more I can do.
claunia commented 2026-01-31 05:32:53 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 13, 2022):

QQ: What graphics card do you have?

@DHowett commented on GitHub (Apr 13, 2022): QQ: What graphics card do you have?
claunia commented 2026-01-31 05:32:53 +00:00
Author
Owner
Copy Link

@Forinil commented on GitHub (Apr 14, 2022):

@DHowett Intel UHD Graphics 620 and AMD Radeon 520. I'm using Dell Inspiron 3576 laptop.

@Forinil commented on GitHub (Apr 14, 2022): @DHowett Intel UHD Graphics 620 and AMD Radeon 520. I'm using Dell Inspiron 3576 laptop.
claunia commented 2026-01-31 05:32:53 +00:00
Author
Owner
Copy Link

@Forinil commented on GitHub (Apr 14, 2022):

I tried to recreate the issue all day today and couldn't. The only thing that changed are some Windows Updates. Either one of them fixed this or the accompanying full system reboot did the trick.

@Forinil commented on GitHub (Apr 14, 2022): I tried to recreate the issue all day today and couldn't. The only thing that changed are some Windows Updates. Either one of them fixed this or the accompanying full system reboot did the trick.
claunia commented 2026-01-31 05:32:54 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 14, 2022):

🤷

Weird. We'll keep our eyes out for other reports, but very glad the issue seems to have gone away!

@zadjii-msft commented on GitHub (Apr 14, 2022): 🤷 Weird. We'll keep our eyes out for other reports, but very glad the issue seems to have gone away!
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-Attention Needs-Tag-Fix Needs-Triage Resolution-No-Repro
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#17126
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?