Fix Issue 14721: TreeView.CustomDraw leaks one HFONT per visible item per paint when NodeFont is set, leading to GDI handle exhaustion and crash#14730
Open
SimonZhao888 wants to merge 3 commits into
Conversation
… per paint when NodeFont is set, leading to GDI handle exhaustion and crash
Contributor
There was a problem hiding this comment.
Pull request overview
This PR addresses a GDI handle leak in TreeView.CustomDraw by avoiding per-paint HFONT creation when TreeNode.NodeFont is set, reducing the risk of GDI handle exhaustion and process crashes during frequent repaint scenarios.
Changes:
- Switches the selected font handle in the custom draw path from a short-lived
OwnerDrawPropertyBaginstance to the node’s long-lived_propBagcache. - Adds guards/asserts around
_propBagusage when selecting the font into the item DC.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #14721
Root Cause
TreeView.CustomDrawcallsGetItemRenderStylesduring everyITEMPREPAINTevent, and this method creates a newOwnerDrawPropertyBag. The original code utilized renderinfo.FontHandle, which triggeredFont.ToHfont()—allocating a newHFONT—whenever the property was first accessed in a new bag. Because these short-lived objects could not be released immediately, GDI font handles accumulated rapidly during high-frequency repainting, eventually leading to handle exhaustion and a crash.Proposed changes
renderinfo.FontHandletonode._propBag.FontHandle, utilizing the reusable, long-lived cache available on theTreeNode. Null checks (fornode._propBagandnode._propBag.Font) are retained to ensure safety. This change preserves standard rendering semantics (using the same font source) while avoiding the repeated creation of anHFONTduring every paint operation.OwnerDrawPropertyBag, changeFontfrom an auto-property to one with a custom setter: when the font changes, explicitly dispose of the old_fontWrapperand set it tonull, ensuring that the correctHFONTis recreated the next timeFontHandleis accessed.Customer Impact
Win32Exception: The operation completed successfully.) and subsequent application crashes (0xC000041D) caused by reaching the 10,000 GDI handle limit.TreeNode.NodeFontat runtime, the new font is correctly reflected, and the oldHFONTis not used.Regression?
Risk
Screenshots
Before
14721-Before.mp4
After
14721-After.mp4
Change the font of a TreeNode:
14721-After2.mp4
Test methodology
Test environment(s)
Microsoft Reviewers: Open in CodeFlow