-
-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Track memory allocations in tests #216
Conversation
Like with SixLabors/ImageSharp#2082 this is mostly about adding in the framework with a single case being fixed to validate the framework works |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks!
When will this version bump be available on nuget? |
It'll be published on our MyGet feed now. See the readme for details. NuGet won't happen until RC now. |
I am in the process of still documenting what I found but I found another instance of |
no we added a framework to enable us to be able to test such issues but it hasn't been introduced everywhere in the tests suite FYI when you have your issue ready make sure you report it over on the main ImageSharp repo (this repo is only for the drawing side and resize is not handled over here) |
@tocsoft |
Prerequisites
Description
Like with SixLabors/ImageSharp#2082 this introduces the test helpers for validating Memory allocations tracked by our memory allocator.
This is dependent on the code in SixLabors/ImageSharp#2082 for the required changes to theMergedMemoryDiagnostics
class to enable this.Also fixes #215