You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There was a time when I needed to render the animation too much and keep calling the cleanup function but this caused a console error. I tried to use cleanupInstance but it sends another console just by rendering the element once.
There was nothing in the document that addressed this issue and this console error keeps popping. I tried to use eventCleanup not to cause a console error but this causes a memory leak for looped rive animations (noninteractive ones), causing the page to crash. I use Vue2, and these clean functions in the destroyed() hook. (I use version 1.1.8)
The text was updated successfully, but these errors were encountered:
Hi @EE539 - do you have a reproducible sandbox you can provide with this scenario so it can be triaged further? Curious if cleanup() is being called twice on the same Rive instance.
Hello, I fixed my problem using these functions: destroyed() { this.rive?.stopRendering(); this.rive?.cleanupInstances(); },
I'm using Vue2, the problem is that when I change something non-stop (because of the way the system was created), our page renders itself (not like F5 or CTRL+shift+R, it just re-renders every element it has). So if anything about an element changes (for example, color), it re-renders every element again. Doing this too much (like changing the color of the element nonstop) created this issue. But when I used stopRendering and cleanupInstances together instead of the cleanup() function, these console errors perished. I don't really know why though. cleanup() also has these functions so I didn't understand what was causing this error (Maybe deleting rive files before it's created but this error comes from the Draw function so I am not sure). I was also wondering if using stopRendering function causes any trouble with the way I used it! (The problem is basically when I create and remove it too fast, and if I am also using the cleanup function, these console errors show up)
There was a time when I needed to render the animation too much and keep calling the cleanup function but this caused a console error. I tried to use cleanupInstance but it sends another console just by rendering the element once.
There was nothing in the document that addressed this issue and this console error keeps popping. I tried to use eventCleanup not to cause a console error but this causes a memory leak for looped rive animations (noninteractive ones), causing the page to crash. I use Vue2, and these clean functions in the destroyed() hook. (I use version 1.1.8)
The text was updated successfully, but these errors were encountered: