Plug the WPF leak... maybe. #5211
Merged
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
retailcoder
reviewed
Oct 13, 2019
| ((Bitmap) source).Save(ms, System.Drawing.Imaging.ImageFormat.Png); | ||
| var image = new BitmapImage(); | ||
| image.BeginInit(); | ||
| image.CacheOption = BitmapCacheOption.OnLoad; |
There was a problem hiding this comment.
This probably explains the increased memory consumption; the bitmaps weight more than the leaked object pointers ;-)
OTOH this eager caching is exactly what permits cleanly disposing the stream.
This was referenced Oct 13, 2019
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.
Closes #4660
Using the advice from this SO thread, this seems to work. However, the memory profiling seems to have paradoxically resulted in a slight memory increase, but that might be due to extraneous factors.
Suggestions welcome to positively prove this helped the matter.