didreceivememorywarning

When the app receives a low memory warning message, 3 situations can happen : your app has just been launched and the user has not done anything special the app is running and there is a current context the app is in the background with some running context So when you receive this message, your are supposed to free memory... But where ? And how ? I understand that : initWith ..... must set the default static values. viewDidLoad must load any non static object didReceiveMemoryWarning must free those non static objects I don't see what can/must be done in viewDidUnload ... I guess some retained

My app has a thread that does some time consuming job for more than a minute and the app consumes around 6.8MB of memory. I receive a memory warning after sometime and then it gets killed. There is nothing that I can release, and I am using not even 7MB of memory...driving me crazy...any advice please? Maybe your memory is super-fragmented? Even 7mb full of leaked data shouldn't kill your app. You ought to have at least 20mb to play with. Try rebooting the phone and see if that helps. I still do not know why it is happening, but now I have a found a workaround. Instead of running this job in a

In new iOS 6, viewDidUnload is deprecated and we have been instructed to use didReceiveMemoryWarning instead, to manage objects in UIViewController instances and subclasses. Is it equally effective to assign nils to UIView kinds inside didReceiveMemoryWarning like the way it has been done inside viewDidUnload ? I am asking this because these two methods seems to be working differently. It seems like didReceiveMemoryWarning doesn't guarantee viewDidLoad to be called again to re-instantiate any necessary UIViews. I suspect with iOS 6, memory management is done without requiring to manually

Whenever I create a new View Controller subclass, Xcode automatically adds the method override func didReceiveMemoryWarning() { super.didReceiveMemoryWarning() // Dispose of any resources that can be recreated } Usually I just delete it or ignore it. This is what all the tutorials I have seen do, too. But I assume that since Xcode gives it to me every time, it should be somewhat important, right? What should I be doing here? I assume that disposing of resources means setting them to nil, but what exactly are "resources that can be recreated"? I have seen these questions: How to implement

I'm new developer about to launch my first app. I'm confused about the deprecation of viewDidUnload as described below in Apple's iOS 6 release notes: In iOS 6, the viewWillUnload and viewDidUnload methods of UIViewController are now deprecated. If you were using these methods to release data, use the didReceiveMemoryWarning method instead. You can also use this method to release references to the view controller’s view if it is not being used. You would need to test that the view is not in a window before doing this. Why is this happening? What guidelines should I follow to ensure that this