Fix slow leak of Pango context objects in drawable update #1801
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.
The change to use the Gtk# Pango (text) context associated with the control instead of creating a new local one on each draw event. The leaked objects would be detected as a slowly growing process memory footprint the rate of which was determined by the amount of Drawable update activity. Tested on several (windows/Linux) platforms for a few hours with stable process memory.
addresses issue #1796