Use Segment Heaps if available #5490
Merged
+2
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use Segment Heaps for memory (de)allocation if available via manifest opt-in (applies to Win10 version 2004 and newer (such as Win11) otherwise falls back to the default NT Heaps). https://learn.microsoft.com/en-us/windows/win32/sbscs/application-manifests#heaptype
rizonesoft
approved these changes
Jan 17, 2026
Owner
rizonesoft
left a comment
rizonesoft
left a comment
There was a problem hiding this comment.
Security Analysis
No executable code | ✅ Only XML manifest modifications
No new dependencies | ✅ Uses built-in Windows feature
Official Microsoft API | ✅ Documented by Microsoft
Backward compatible | ✅ Falls back to NT Heaps on older Windows
No hidden characters | ✅ Clean diff
Technical Benefits
- Memory reduction: Segment Heap is a modern heap implementation that reduces overall memory usage
- Less fragmentation: Improved memory allocation strategy
- Windows 10 2004+ only: On older systems, Windows ignores the setting and uses the default NT Heap
Compatibility
- Windows 10 version 2004+ / Windows 11: Uses Segment Heap
- Older Windows versions: Gracefully ignored, uses standard NT Heap
Verdict
This is a low-risk, high-value optimization. The change is minimal, uses an official Microsoft manifest setting, and provides automatic fallback for older systems. Recommended to merge. 👍
rizonesoft
added a commit
that referenced
this pull request
Jan 17, 2026
Changes: - Moved installer scripts to Build\Installer folder with local language files - Fixed user config setup to run as original user context (ExecAsOriginalUser) - Added Segment Heap memory optimization (PR #5490) - Updated .gitignore to exclude .agent folder - Created todo folder with Scintilla/Lexilla upgrade research
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use Segment Heaps for memory (de)allocation if available via manifest opt-in. This applies to Win10 version 2004 and newer (such as Win11) otherwise falls back to the default NT Heaps. https://learn.microsoft.com/en-us/windows/win32/sbscs/application-manifests#heaptype
Testing shows that this reduces memory usage a little bit. attributes related to memory fragmentation have not been tested however Segment heaps are supposedly better in this regard as well.
!heapin WinDbg can be used to confirm that the memory heaps of the process(es) are indeed being allocated with the newer heap type.