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
We have a single-page react application using rappid and joint libraries. The components that use rappid functionality are not being garbage-collected. When I investigated memory snapshots I see that the object roots are in SVG-prefixed 'window' properties. What can I do to prevent such behaviour? We use rappid version 2.4.0(joint 2.2.1).
The text was updated successfully, but these errors were encountered:
Sorry for asking question here rather than new an issue. (I'll do so if necessary)
Actually, I am facing similar memory leaks issue recently.
I'm using Angular 8 rather than the React. (and JointJS 3.1.1)
In my case, I do add paper.remove() and print logs in ngOnDestory(), which means those papers should have called remove() correctly when route to other pages.
However, there are still thousand of leaks here and I don't know how to fix it... (I even call graph.clear() at the same time but still don't work)
We have a single-page react application using rappid and joint libraries. The components that use rappid functionality are not being garbage-collected. When I investigated memory snapshots I see that the object roots are in SVG-prefixed 'window' properties. What can I do to prevent such behaviour? We use rappid version 2.4.0(joint 2.2.1).

The text was updated successfully, but these errors were encountered: