One of the great things about JavaScript, and other high-level languages, is that we don’t have to manually allocate and free memory. Instead, we use memory more or less without thinking about it, relying on the garbage collector to do the hard work for us. However, this doesn’t mean that we no longer have to think about memory at all; we can still have memory leaks, as well as allocate more memory than we thought, if we’re not aware of how the language really works In this talk, Samuel Saccone where and how memory problems can arise, and (even more significantly) how we can track down and debug them.