fuite

A CLI tool for finding memory leaks in web apps, particularly SPAs. Use a single command to test any URL for leaks.

How fuite works:

‘fuite’ launches Chrome using Puppeteer, loads a web page, and runs a scenario against it. It runs the scenario some number of iterations (7 by default) and looks for objects that leaked 7 times (or 14 times, or 28 times).

This might sound like a strange approach, but it’s useful for cutting through the noise in memory analysis.

fuite looks for the following leaks:

• Objects (captured with Chrome heap snapshots)
• Event listeners
• DOM nodes (attached to the DOM – detached nodes will show under ‘Objects’)
• Collections such as Arrays, Maps, Sets, and plain Objects

The default scenario clicks internal links because it’s the most generic scenario that can be run against a wide variety of SPAs, and it will often catch leaks if client-side routing is used.