TechPrufer
Get started
Meta
Meta logoMeta · Feature trail

JavaScript Memory Leak Detection Framework

2 posts · Apr 2016 – Sep 2022

What this trail covers

Meta has open-sourced MemLab, a JavaScript memory testing framework that automates memory leak detection. MemLab helps engineers and developers identify and root-cause memory leaks in web applications by running headless browsers through predefined test scenarios, diffing JavaScript heap snapshots, generating retainer traces, and clustering them for analysis. It provides a graph-view API for JavaScript heaps and supports memory assertions for self-memory checking in Node.js or Jest tests. Meta has used MemLab to successfully contain unsustainable memory increases and identify memory leaks and memory optimization opportunities across its products and infrastructure.

All Meta trails
  1. MemLab: An open source framework for finding JavaScript memory leaksThis post introduces MemLab, an open-source JavaScript memory testing framework designed to automate memory leak detection and root-cause analysis. It details the six-step process of how MemLab works, including browser interaction, heap diffing, retainer trace generation, and clustering. The post also highlights MemLab's features such as memory leak detection, a graph-view API of JavaScript heaps, memory assertions, and a memory toolbox with CLI commands and APIs for finding memory optimization opportunities. It explains the technical challenges of managing client-side memory in SPAs and how MemLab addresses these by providing a scalable solution beyond manual debugging with DevTools.
  2. Automatic memory leak detection on iOSThis post details the development and open-sourcing of three tools for automatic memory leak detection on iOS: FBRetainCycleDetector, FBAllocationTracker, and FBMemoryProfiler. FBRetainCycleDetector uses Objective-C's runtime introspection (ivar layouts, type encoding) and a block ABI analysis (with release detectors) to find retain cycles. FBAllocationTracker proactively tracks object allocations/deallocations to provide candidate objects for the detector. FBMemoryProfiler offers manual profiling with 'generation tracking'. The post also describes a backend algorithm for clustering retain cycles and using 'git/hg blame' to identify the likely introducer of a leak.