[ios] fix memory leak in Stepper
#18663
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
Context: dotnet#18365 Adding a parameter to the test: [Theory("Handler Does Not Leak")] [InlineData(typeof(Stepper))] public async Task HandlerDoesNotLeak(Type type) Shows a memory leak in `Stepper`, caused by the cycle * `StepperHandler` -> * `UIStepper.ValueChanged` event -> * `StepperHandler` I could solve this problem by creating a `StepperProxy` class -- the same pattern I've used in other PRs to avoid cycles. This makes an intermediate type to handle the events and breaks the cycle. Still thinking if the analyzer could have caught this, issue filed at: jonathanpeppers/memory-analyzers#12
jonathanpeppers
added
platform/iOS 🍎
memory-leak 💦
ghost
added
the
legacy-area-controls
rmarinho
approved these changes
Nov 10, 2023
21 tasks
Eilon
removed
the
legacy-area-controls
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Context: #18365
Adding a parameter to the test:
Shows a memory leak in
Stepper, caused by the cycleStepperHandler->UIStepper.ValueChangedevent ->StepperHandlerI could solve this problem by creating a
StepperProxyclass -- the same pattern I've used in other PRs to avoid cycles. This makes an intermediate type to handle the events and breaks the cycle.Still thinking if the analyzer could have caught this, issue filed at:
jonathanpeppers/memory-analyzers#12