Avoiding zoombie screens and memory leaks in backbone architecture
Backbone.js promotes single page architecture.
When switching subview of the backbone app there is always a risk of the old view being not released properly and leaving resources in the browser memory. This has deadly consequences for the application that will slow down initially and then crash/stall browser. This situation is even more severe on mobile platforms.
Solution implementing a destructor for each view that would trigger a cleanup code of distractors. Here is a link to the article that provides description of the solution: