Memory leak

To address memory leaks, it's important to understand the concept of reachability. Memory in your program should be reachable through non-weak references to be used in the future. There are three types of memory on your heap:

1. Useful Memory: Reachable and will be used again.
2. Abandoned Memory: Reachable but won't be used again, contributing to wasted memory.
3. Leaked Memory: Unreachable and can't be used again, often due to lost pointers or reference cycles.

To fix memory leaks, you can:

• Remove accidental references.
• Change ownership qualifiers from strong to weak or unowned.

For investigating leaks, you can use the "show only leaked allocations" button in Xcode's memory graph debugger. This helps identify reference cycles, such as those involving Swift closure contexts, which can be resolved by specifying a capture list (weak or unowned) to break the cycle.

For more detailed information, you can refer to the session Analyze heap memory (20:15) which covers reachability and ensuring memory is deallocated appropriately.