fix(android-animations): reuse animatorSet to prevent high memory usage #6930
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.
Do not recreate native animators when looping animation inside keyframe animation.
Android API > 23: Reusing animatorSet instead of recreating it on every animation iteration. This results in even less memory usage. Recreating it on every loop will lead to higher memory peaks (that will be collected a bit later by the GC)
Side note:
pulse
CSS animation consist multiple keyframes that animate the scale of an object to different values in a different times. New Animation is created for every keyframe in the keyframes rule. These animations (keyframes) will play sequentially and will repeat all together for specified iterations (orinfinite
). Every Animation (keyframe) has a AnimatorSet that holds multiple Animators depending on the number of properties it should animate. We do not want to recreate these Animators on every Animation (keyframe) replay.Fix #5731