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

Diskspace #22957

New Issue
Closed
opened 2026-01-31 08:28:24 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 08:28:24 +00:00
Owner
Copy Link

Originally created by @inoperable on GitHub (Feb 20, 2025).

Windows Terminal version

No response

Windows build number

No response

Other Software

No response

Steps to reproduce

Pushed the Build button

Expected Behavior

Sane disk space usage

Actual Behavior

I was literally baffled after Visual Studio told me I runt out of Disk Space when compiling the Terminal.
After closer examination the obj take ~ 60GB for compiling the App.

Does one really need 60GB to compile the Windows Terminal?

Originally created by @inoperable on GitHub (Feb 20, 2025). ### Windows Terminal version _No response_ ### Windows build number _No response_ ### Other Software _No response_ ### Steps to reproduce Pushed the Build button ### Expected Behavior Sane disk space usage ### Actual Behavior I was literally baffled after Visual Studio told me I runt out of Disk Space when compiling the Terminal. After closer examination the obj take ~ 60GB for compiling the App. Does one really need 60GB to compile the Windows Terminal?
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 08:28:24 +00:00
claunia commented 2026-01-31 08:28:25 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 20, 2025):

Unfortunately, it does take rather a lot of disk space. The biggest cost during the build is the precompiled headers produced in projects that consume C++/WinRT.

There have been a few efforts to reduce the sheer disk space cost (e.g. using C++ modules or having one shared precompiled header project,) but all of them come with other tradeoffs:

  • modules cannot be used as they are apparently not mature or supported by the MSBuild C++ build system
  • precompiled header projects break the developer inner loop and cause incidental recompilation of the rest of the project.

I'm somewhat surprised at the 60 GiB figure, though. My final objects directory for a single architecture and configuration combo consumes only 20 GiB, with bin adding only 2 more.

Can you share more about your build environment? What are the largest files there? Are you building all three architectures/?

@DHowett commented on GitHub (Feb 20, 2025): Unfortunately, it does take rather a lot of disk space. The biggest cost during the build is the precompiled headers produced in projects that consume C++/WinRT. There have been a few efforts to reduce the sheer disk space cost (e.g. using C++ modules or having one shared precompiled header project,) but all of them come with other tradeoffs: - modules cannot be used as they are apparently not mature or supported by the MSBuild C++ build system - precompiled header projects break the developer inner loop and cause incidental recompilation of the rest of the project. I'm somewhat surprised at the 60 GiB figure, though. My final objects directory for a single architecture and configuration combo consumes only 20 GiB, with `bin` adding only 2 more. Can you share more about your build environment? What are the largest files there? Are you building all three architectures/?
claunia commented 2026-01-31 08:28:26 +00:00
Author
Owner
Copy Link

@inoperable commented on GitHub (Feb 20, 2025):

@DHowett Thank you for the quick answer, after looking into subdirs its split into 3 x 20GB so it comes to your count, summed up its 60GB because of Debug/Release/Arch combined.

Still, there is something seriously wrong with tooling if you need 20GB+ to compile a terminal emulator (allthough I get this falls outside of the project itself)

@inoperable commented on GitHub (Feb 20, 2025): @DHowett Thank you for the quick answer, after looking into subdirs its split into 3 x 20GB so it comes to your count, summed up its 60GB because of Debug/Release/Arch combined. Still, there is something seriously wrong with tooling if you need 20GB+ to compile a terminal emulator (allthough I get this falls outside of the project itself)
claunia commented 2026-01-31 08:28:26 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 20, 2025):

I know. It sucks.

@DHowett commented on GitHub (Feb 20, 2025): I know. It sucks.
claunia commented 2026-01-31 08:28:26 +00:00
Author
Owner
Copy Link

@inoperable commented on GitHub (Feb 20, 2025):

@DHowett you can del this, nothing to be done about it and no need to add to the pile

@inoperable commented on GitHub (Feb 20, 2025): @DHowett you can del this, nothing to be done about it and no need to add to the pile
claunia commented 2026-01-31 08:28:26 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 20, 2025):

Honestly, I want to keep it around because it creates an evidence trail! "It's not just Microsoft developers who hate this - contributors do too!" 🙂

@DHowett commented on GitHub (Feb 20, 2025): Honestly, I want to keep it around because it creates an evidence trail! "It's not just Microsoft developers who hate this - contributors do too!" 🙂
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-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#22957
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?