Do not assert callbacks contains key if disposed #104292
Merged
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 first added test passes with or without this patch, but was missing coverage.
The second added test fails without this patch. When a layer is disposed it clears its callbacks to avoid a potential memory retain.
I ran into this working on visibility_detector, which is trying to cancel its callback in a
RenderObject.disposemethod, which may end up firing after the layer is disposed.