Hunting memory leaks in JavaScript using Chrome DevTools

Hunting memory leaks in JavaScript using Chrome DevTools

January 23, 2018

Hunting memory leaks in JavaScript using Chrome DevTools

Have you ever left a web app opened in a tab for a couple of hours to come back and see this screen? In this post we will learn how to use the Chrome DevTools to find memory leaks.

Memory management

JavaScript is a garbage collected language, but we should still learn about memory management, as making memory leaks in your code is quite easy. In short the garbage collector tracks memory allocation and when a piece of allocated memory is not needed any longer, it frees it. Unreachable pieces of memory are considered garbage, but for the rest only the developer can decide whether it’s needed or not. So, the main causes of memory leaks in JavaScript are unwanted references like accidental global variables, forgotten intervals, detached DOM elements and others.

Visualize using Timeline

Can you spot a problem with the following code snippet?

Don’t worry if you can’t figure it out, the issue is not so obvious. To diagnose if an application has a memory leak, you can use the Performance section in Chrome DevTools. In the above example we want to check if continuous usage of the application (adding/removing tasks) causes unexpected increase of memory usage. To test this we can record the memory usage while adding and removing a task several times. We expect that when we add a task the memory usage increases and when we remove it – the memory usage drops back to the previous level.


  1.  Start a recording
  2. Add a task
  3. Remove the newly added task
  4. Click on “Collect garbage
  5. Go back to 2.
  6. When you perform this a few times stop the recording and look for patterns that grow as shown in the screenshot:

memory leaks

As seen on the screenshot above the nodes and listeners progressively increase and never drop while the expected outcome is a graph similar to the JS Heap line above.
Note that garbage collection is non-deterministic. In other words, it is not possible to be certain when a collection will be performed, so Chrome DevTools gives us an option to force it (step 4).

Discover detached DOM using Heap Snapshots

When it comes to finding where the problem originates the Memory section in Chrome DevTools comes in handy. With a couple of snapshots we can find which parts of the application use more memory than expected and whether we have any detached DOM elements:
memory leaks

  1. Reload the page.
  2. Take a heap snapshot
  3. Add a few tasks and remove them
  4. Take another heap snapshot
  5. Compare the two snapshots and you’ll see the second one uses more memory although we have removed all tasks.
  6. Expand the “Detached DOM tree” list and you will see there are still references to the DOM elements that were removed (marked in red).

memory leaks

Turns out our Task’s destroy method has a bug – we call the DOM removemethod, but we still keep a reference to the DOM element, so it’s never collected. When we get that fixed and perform the same test in the Performance tab, we’ll see the pattern we want:
memory leaks
The overall memory usage is proportional to the number of tasks we have and removing tasks actually drops the memory usage.


Memory leaks are common in JavaScript. Some of them may cause serious performance issues, so it’s a good idea to get familiar with memory management and start profiling at an early stage, especially when working on big applications. In this article we’ve only scratched the surface, but it’s still a good start.


Here you can get the fully working examples:

Do you want more great blogs like this?

Subscribe for Dreamix Blog now!