We covered some aspects of the theory of memory management, such as retain cycles and strong/weak references. Then, we moved to the repercussions of memory leaks and the various warning levels. Following this, we discovered how to get crash logs to help you get information about your app and code. We then looked at a list of the various tools that Xcode possesses, such as Instruments and NSZombies, which will help us to debug memory leaks that can be caused by a myriad of causes, such as not releasing objects or releasing objects prematurely. Finally, we closed off with a description of static analysis and enabling NSZombies and their uses. With all these tools and information at your fingertips, I hope debugging memory leaks and errors have been made much easier for you since you have the tools required to make this a less painful journey.

In the next chapter, we will cover some developer tips for memory management, such as getters, setters, and other tips. So, let's head to the...