Do you have memory leaks in your backbone?

Question

JavaScript

Iconto's front-end programmer assured that the backbone "flows" wildly, so you need to use marionette
. Is this true in real projects?
I have never seen anything like this in my practical work.

Answer 1

The backbone had problems with nested views. Example: You have a parent view that has child views nested within it. What happens if the parent view is deleted? Child views will remain in memory, and this is where it actually flows. But this is no longer a matter of the backbone, but of the developer's hands.
Or you can remove the container of another view from one view, it will also leak, but this is also a handshake.
There is nothing to leak in Model and Collection.
Marionette.js provides a set of view entities that are truly leak-safe. But even they do not guarantee the handshake of the developer.
In my memory, there were still dances with jQuery UI widgets, which were initialized each time. But it's about handshaking again.
So you should check with a respected iconto front-end programmer for handshake. Maybe the backbone is not to blame for anything.

Answer 2

Marionette is a backbone extension, they don't write anything about memory on their website...