I ported some old code over to Objective-C ARC (Automatic Reference Counting) and it seems to work great. Except a rather large, high-level object is not being deallocated when it is popped off of my navigation stack, making me believe I have a retain cycle somewhere that ARC has hidden from me (or at least made difficult to track down). What is the best way to weed out this potential retain cycle and/or what is a good way to determine the cause of a memory leak under ARC? Thanks!
The best way is usually to use the Leaks instrument in the Instruments app.
The What's New In Instruments video from WWDC 2011 discusses using Instruments to find retain cycles under ARC, starting about 38 minutes in.
I just transitioned an older app to use ARC. Instruments showed no leaks, but the allocations continued to go up. I found that by looking at the live objects for something that I knew should be deleted, I was able to track down the retains without a release. Here are the basic steps:
- Use the Allocations tool in Instruments
- Play with your app for a while (if you know what isn't being released, this goes faster)
- Change Statistics to Objects in the Allocations jump bar
- Sort by Category and find the class name of your unreleased object
- Find a living instance and click the little right arrow next to the memory address
- Now you can see the history of retains and releases for an object
X-code 8 introduced the Memory graph debugging tool: 
have a look here for full reference:
来源：https://stackoverflow.com/questions/9139619/arc-circular-retain-detection