Stop. Just stop. Never look at the retainCount
of an object. Ever. It should never have been API and available. You’re asking for pain.
There’s too much going on for retainCount
to be meaningful.
More Related Contents:
- When to use -retainCount?
- Why is @autoreleasepool still needed with ARC?
- Retain cycle on `self` with blocks
- Why would you use an ivar?
- Class methods which create new instances
- How does the NSAutoreleasePool autorelease pool work?
- Weak NSString variable is not nil after setting the only strong reference to nil
- In which situations do we need to write the __autoreleasing ownership qualifier under ARC?
- How is release handled for @synthesized retain properties?
- With ARC, what’s better: alloc or autorelease initializers?
- Tagged pointers in Objective-C
- What is the cost of using autorelease in Cocoa?
- Does @”some text” give an autoreleased or retain 1 object back?
- What increases an object’s retain count?
- What is the difference between a __weak and a __block reference?
- Xcode 6 and Embedded Frameworks only supported in iOS8
- Phone number formatting on iOS
- How can I add properties to an object at runtime?
- Objective-C: `@synthesize fooBar;` vs. `@synthesize fooBar=_fooBar;` [duplicate]
- If “a == b” is false when comparing two NSString objects
- Get property name as a string
- Track all ObjC method calls?
- Objective-C: Where to remove observer for NSNotification?
- How to dispatch on main queue synchronously without a deadlock?
- What is the difference between ‘->’ (arrow operator) and ‘.’ (dot operator) in Objective-C?
- How to write regular expressions in Objective C (NSRegularExpression)?
- Objective-C call function on another class?
- Bullet list and Numbered list in UITextView
- Xcode linker error: file too small for architecture x86_64
- “Expression is not assignable” — Problem assigning float as sum of two other floats in Xcode?