V1.2.x Fix leak of gc's in gtkagg backend. #1484
Closed
Conversation
This file contains 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
removed setup.py print statement.
Remove all mention of make.osx in README.osx
agg_buffer_to_array.py crashes
Remove John Hunter's email from mpl docstring
Colorbar edges are different in PDF backend
pgf: documentation fixes
Document the Gtk3 backends
This reverts commit 8d61cd4.
This reverts commit d1fda6e.
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.
The gtkagg backend leaks gc's. They are created with gdk_gc_new(drawable); but never destroyed.
This commit destroys the gc's and fixes the memory leak.
sorry - I'm a total newbie at git. Let me try again.