Memory leak - ValueAnimator holding a reference to the view
dorsamet opened this issue · comments
Hi,
I received this memory leak:
I've seen a similar issue being posted on the Facebook Github.
We currently extend the layout to play around with the animation (delay start, have it play for a bit, and then stop it). While this manipulation of the animation does require a reference to the view, I am having a hard time understanding why, since the view doesn't reference the handler holding a reference to a message, and so on.
WDYT?
@dorsamet If you could show/send me code I could check it. Basically, the lib should not leak memory as when it is detached, all the bitmaps are recycled, animation is cancelled and listeners also removed.
Since no other information about the leak has arrived, I am closing this issue.