automatic-ref-counting

I have a UIViewController that is pushed onto a container controller and then popped off, and using the allocations instrument, I can see that the view controller is destroyed afterwards. However, a breakpoint in the controller's dealloc is never reached. Does anyone know why dealloc isn't called? Is it possible for ARC to destroy an object without calling dealloc? Also, I've disabled NSZombies (some have said that can cause dealloc not to fire). Edit: Dealloc doesn't do much, just prints to the console, and it never gets called: - (void)dealloc { NSLog(@"Deallocating..."); } I can't post the

I have an object that is being retained more than necessary (most likely due to a property that is strong instead of weak ). Big codebase, so it's hard to find where. How can I find all the lines in which this object is being retained when using ARC? If I weren't using ARC I guess I could simply override retain and check from where it's called. Can I do something similar with ARC? bbum To track growth of an application, Heapshot Analysis has proven very effective. It will capture both true leaks and accretion of memory where the allocations are not accounted for by leaks. You can see all of

I used to verify that some of my variables had the expected retain count using [myVar retainCount] under the debugger, especially for var that did not have a custom dealloc. How do you do this in ARC mode? How do you ensure that there are no memory leaks? Note: I understand that ARC should handle this for me, but life is far from being perfect, and in real life you have objects that are sometimes allocated by third party libraries (using retain?) and never deallocated. Image that I do this: MyObj *myObj=[[MyObj alloc] init]; then I call [somethingElse doSomethingWithMyObj:myObj]; and later, I

I am trying to figure out a way to use typeof to create a weak reference to self for use in blocks to avoid retain cycles. When I first read about this it seems that the convention was to use __block typeof(self) bself = self; , which compiles but using __block to avoid retain cycles doesn't work anymore and __weak should be used instead. However __weak typeof(self) bself = self; results in an error: The type 'typeof (self)' (aka 'TUAccountsViewController *const __strong') already has retainment attributes set on it Is there a way to use typeof or another call to generically create a weak

I've begun developing my first iOS app with Xcode 4.2, and was targeting iOS 5.0 with a "utility application" template (the one that comes with a FlipsideViewController). I read that since ARC is a compile-time feature, it should be compatible with iOS 4 as well, so I attempted to target my app to 4.3, and try compiling it. When I do so, I get this error: FlipsideViewController.m: error: Automatic Reference Counting Issue: The current deployment target does not support automated __weak references It is referencing this line: @synthesize delegate = _delegate; That variable is declared as:

I'm currently using the iOS 5 SDK trying to develop my app. I'm trying to make an NSString a property, and then to synthesize it in the .m file (I have done this before with no issues). Now, I came across this: "Semantic Issue: Property's synthesized getter follows Cocoa naming convention for returning 'owned' objects." This is my code: .h @interface ViewController : UIViewController { NSString *newTitle; } @property (strong, nonatomic) NSString *newTitle; .m @synthesize newTitle; Does anyone have a clue how I could fix this? Thanks!! My guess is that the compiler version you’re using follows

I have thousands of line of code written for iOS 4. The codebase contains many calls to retain and release , which cause errors when the project is updated to iOS 5 and ARC. Is there a way to automatically convert Manual Retain-Release (MRR) code to Automatic Reference Counting (ARC)? In Xcode 6+, the command is now: Edit > Convert > To Objective-C ARC... From the Xcode 4.2 release notes : To initiate the process, enable Continue building after errors in the General Preferences pane, then choose Edit > Refactor > Convert to Objective-C ARC . The targets that you convert are updated to build

What is the proper way to add objects in NSMutableArray which is strongly defined by property. [tapBlockView setTapBlock:^(UIImage* image) { [self.myImageArray addObject:image]; // self retain cycle } If I will create weak reference something like __weak NSMutableArray *array = self.myImageArray; [tapBlockView setTapBlock:^(UIImage* image) { [array addObject:image]; // If I will do this then how will I update original Array ? } I have also tried __weak id weakSelf = self; [tapBlockView setTapBlock:^(UIImage* image) { [weakSelf storeImageInaNewMethod:image]; // Calling SToreImageInaNewMethod }