Please enable JavaScript.

Coggle requires JavaScript to display documents.

memory leak - Coggle Diagram

- - - - Scavenge collection: Fast and runs on the Young Generation.
      - Mark-Sweep collection: Slower and runs on the Old Generation.
    - - New Space
        
        Where new allocations happen. Garbage collection is quick. Has a size of between 1 and 8 MBs. Objects in the New Space are called the Young Generation.
      - Old Space
        
        Where objects that survived the collector in the New Space are promoted to. Objects in the Old Space are called the Old Generation. Allocation is fast, however, garbage collection is expensive and infrequent.
- - - - are never garbage collected throughout the lifetime of an app. They occupy memory as long as the app is running.
    - - If you reference the same object from multiple objects, it can lead to a memory leak if one of the references is garbage collected while the other one is left dangling.
    - - When a closure holds a reference to a large object in heap, it keeps the object in memory as long as the closure is in use.
      - This implies easily ending up in situations where a closure holding such a reference can be improperly used leading to a memory leak.
    - - The use of setTimeout, setInterval, Observers, and event listeners can cause memory leaks when heavy object references are kept in their callbacks without proper handling.