How we wrote the Sealant framework to look for memory leaks in JS

In the age of single-page web apps, memory leaks in JS became the ultimate bane. Usually this problem gets covered from the development side, and advices on how to analyze already existing memory leaks are provided. But what to do when you have to find these leaks in advance in a large app?

In this session, we'll discuss how in Tensor they test their products for memory leaks. We will:

• cover the usual approach — DevTools and three snapshot technique;
• discuss in detail autotests checking scenarios for the leaks, using Selenium and Сhrome Debugging Protocol;
• investigate memory leak through memory-infra, when even DevTools can't do a thing;
• analyze access logs to find critical errors with memory leaks.