automatic-ref-counting

First off, thank you to everyone on this site...it's been INCREDIBLY helpful in getting into the grit of iOS programming. My current issue: I have an app that renders a very stylized version of a photo. It uses some CoreImage filters for some of it, but needs a bunch of CoreGraphics to get the heavy image processing done. The proxy size renders work out great, but when I render a full resolution version of my image, it sometimes crashes because of high memory usage. The problem is that I need to be able to have several full resolution (3264x2448) buffers in memory when rendering. I don't know

Are there a differences between these two lines of code? __weak IBOutlet UITextField *usernameField; @property (weak) IBOutlet UITextField *usernameField; What if you declare either of these in interface section of the .h or the .m files? Yes. The first example declares a weak instance variable called usernameField , but the second declares a weak property called usernameField , and an instance variable called _usernameField that is accessed by the property. If you declare it in an @interface section of the .m file, then it can only be accessed in that .m file (unless you mess with the

I'm using the Pinterest iOS SDK to share an item in my iPad app. The following snippet of code will always crash with a message sent to deallocated instance on the line with the comment: NSString *clientId = [NSMutableString stringWithString:@"1431665"]; NSLog(@"clientId: %@", clientId); Pinterest *pinterest = [[Pinterest alloc] initWithClientId:clientId]; NSLog(@"gone: %@", clientId); // <- CRASH! I'm using NSMutableString stringWithString to simulate the conditions in my app. I don't actually use that line in my code. Even if don't output the clientId on the last line, the app crashes when

From inside an event handler of the control itself, I would like to delete and free it. A typical use case for TFmxObject.Release , isn't it? However, it only seems to work under Windows, but not Android, and this method is now deprecated anyway. I know, doesn't work is not a good problem description, but currently I'm not able to debug it under android. Under Windows, I see that the event handler continues correctly after the .Release and after it finished, my log message inside my controls destructor is executed. Under Android, the application hangs. When I use .Free instead, it still works

I have a doubt regarding weak property in ARC (auto reference counting) My understanding (correct me if I am wrong): weak property behaves similar to the assign property except that when the instance that the property was pointing to gets destroyed, the ivar is made to point to nil. Question: I just feel that the getter of the weak property retains and autoreleases. Isn't it suppose to behave like getter of the assign property where the getter doesn't retain and autorelease ?(pls refer to the program) Program: I have given below the program with the actual output and my expected output. Note -

If I run the following in a project where ARC is enabled the completion handler never fires. But without ARC it works as expected. What am I missing here? NSURL *url = [NSURL URLWithString:@"http://media.w3.org/2010/05/sintel/trailer.mp4"]; AVURLAsset *asset=[[AVURLAsset alloc] initWithURL:url options:nil]; AVAssetImageGenerator *generator = [[AVAssetImageGenerator alloc] initWithAsset:asset]; generator.appliesPreferredTrackTransform = YES; CMTime thumbTime = CMTimeMakeWithSeconds(5,30); AVAssetImageGeneratorCompletionHandler handler = ^(CMTime requestedTime, CGImageRef im, CMTime actualTime,

This is weird. I've got a super simple project to learn NSTableView, and it's set up in my nib, set as a View-based tableView. I've also set the dataSource and delegate to my controller obejct. When I do this, however, and run, I get an EXC_BAD_ACCESS, with the trace starting in my main function and the rest of the stack is internal to Cocoa (so not my code). There's really nothing fancy going on, other than this project is using ARC (it's a new project, so this was the default). I also tried using the Analyzer to make sure I wasn't improperly doing memory managment anywhere and there were no