MemoryLeak in LottieDrawable

In LottieDrawable consturction method, it will auto add a annoyous update listener and refer the drawable and context, cause the activity leak. How to remove the update listener to avoid memory leak?

animator.addUpdateListener(new ValueAnimator.AnimatorUpdateListener() {
      @Override public void onAnimationUpdate(ValueAnimator animation) {
        if (compositionLayer != null) {
          compositionLayer.setProgress(animator.getValue());
        }
      }
    });

[gpeal]

Newer versions of Lottie will unschedule the drawable when it is detached from the window.

[zjupure]

It is dumped from online data and not easy to produce. I read ValueAnimator source and have some suspects. When animator is scheduled, AnimationHandler singleton will hold the reference to ValueAnimator. Until animator is canceled or stopped, AnimationHandler will remove the reference. So it might have a case:

1. lottie animation is playing, AnimationHandler hold it.
2. activity is destroyed, the animation not be canceled or stopped, it will be scheduled in background util end. There will be a bit time memory leak cause that activity cannot be recycled by GC.
3. How long the leak time is decided by animation left duration.

To avoid this case, we manually call LottieAnimationView#cacelAnimation() in activity#onDestory() lifecycle callback. It release the reference from AnimationHandler to ValueAnimation.