How to identify and/or deal with potential memory leaks?

What is JourneyApps’s recommendations identifying and/or dealing with potential memory leaks?

The platform if used nominally, should in almost all cases prevent the user from memory leaks, but it is not a catch all. Most of the issues could and most likely arise from external code which is pulled in. For example, stale HTML DOM elements and listeners (window.addEventListener) etc. are almost always the cause.

We recommend, to anyone that is interested in these kinds of issues, to spend some time learning and getting familiar with the Chrome memory profiler.