animation.destroy() clean up about lottie-web HOT 9 CLOSED

@Tolmark12 Thanks, I'll take a look at it. So you're using the svg renderer and you have png images animating?

from lottie-web.

Yeah, some of the time. The vector assets were sometimes so complex, that replacing them with pngs was needed to speed things up.

from lottie-web.

@bodymovin I just downloaded the new lib and ran a test, and as far as I can tell, it looks like items remain in RAM even after destroying an animation. See the following video for clarity : https://www.youtube.com/watch?v=5oUGoqLMczY

from lottie-web.

Any data, or DOM elements that have a variable with it's value assigned to that item (a pointer) won't be removed from RAM during garbage collection. Event handlers can be especially troublesome. ie: if you set an event handler on some object and even remove all pointers, but don't remove the event listener, the object won't be garbage collected

(Just tell me to shut up if you already know all this :-)

from lottie-web.

@Tolmark12 yes, every reference to dom elements should be removed when calling destroy. I'll keep looking into it.

from lottie-web.

I think all the dom elements may be cleared, but maybe there is data elements still in memory?

from lottie-web.

Hi I am still having this issue even though it apparently got fixed?

from lottie-web.

@1pocketaces1 hi, can you share a link with the issue and more details about it?

from lottie-web.

So after more research and trials I found out that it is necessary to call the animation.destroy() inside the angular component onDestroy() for every animation used in the component. Doing this will work in cleaning up the heap, but if this is not done, then the memory is lost. Thanks for responding!

from lottie-web.