I’ve spent the last four months working on a fairly large HTML5 project that was to run across mobile, tablet, and desktop. For the most part, the project went pretty smoothly but we did notice we were experiencing crashes on low-end devices that we suspected were being caused by memory leaks.

To verify this and to help identify the source of the leaks we turned to Chrome’s memory profiling dev tools. It wasn’t something I had much experience with but this excellent video got me up and running very quickly. The video gives a very good introduction to the basics of JavaScript memory management before diving into Chrome’s Heap Profiler.

Additionally, I found the following two articles extremely useful too:

So if you don’t know where to start when it comes to memory profiling your JavaScript projects then hopefully you’ll find these resources as useful as I did.

  1. Thanks for posting these. I’ve just finished converting some old starling projects to html5 pixi/typescript and was doing my best to cleanup each screen but this will come in handy going forward.