Marionette: Shall We Dance?
summary
Discusses memory leaks in Marionette apps caused by views or models remaining referenced in collections and a global mediator, and identifies the exact references that prevent garbage collection. Demonstrates switching from request/response to command patterns to change coupling (commands are one-to-many, requests one-to-one), reproduces a leak with retained instance objects, and shows removing the binding so GC can free them to prove the fix.
AI-written summary · about
chapters (9)
- 0:00Marionette intro
- 3:11App architecture issues
- 8:05Marionette for cohesion
- 12:09Commands and events
- 19:16Marionette benefits
- 22:25Event types and handling
- 26:30Command handling example
- 31:29Marionette integration tips
- 34:32Q&A
related talks
19mUnderstand, find, prevent and fix memory leaks in JavaScript
24mTrash Talk - Understanding Memory Management
20mMemory Leaks and the Havoc They Wreak
35mAnalyze the JS Heap and detect Memory Leaks
40mClient Side MVC and The Gosh Darn Back Button
21mMemory: Don't Forget to Take Out the Garbage
29mJS Memory Management and Garbage Collection
15mYou Might Not Need Classes