Photo by ika ika on Unsplash

  • Finding memory leaks

    A JavaScript leak is memory the program can still reach but will never use again. This page is the procedure for finding one: confirm the growth survives garbage collection, use heap snapshots to find what is retained and by what, then fix the reference. It ends with the causes behind most leaks.

    · Languages / JavaScript Core / Under the Hood

  • Memory management and garbage collection

    JavaScript gives you no way to free memory, only ways to stop referring to it. This chapter explains what the heap holds, how a tracing collector decides what is garbage, why V8 splits the heap into generations, how heap limits and weak references work, and why cleanup of files and sockets cannot be left to the collector.

    · Languages / JavaScript Core / Under the Hood

Search articles

Type a word to search published articles.

Open the search page