Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am trying to improve memory management in an iPhone app. It’s helped to set IBOutlets to nil in viewDidUnload, but I’m wondering if I need to do any memory management around the static UIImageView’s in my nib’s which aren’t hooked up to any IBOutlet. Or does iOS take care of them well by itself?
Generally you do not need to worry about managing any assets that aren’t attached to an outlet — including UIImageView assets — in NIBs. They will released when the view is released.
If you have any concerns about how memory is being used and released in your app, your best bet is to use instruments to profile memory consumption when the view controller in question loads and unloads. You should see memory increase when the VC loads and drop back to previous levels when the VC is released. If you load/unload the VC many times and you see a steady increase in memory usage, that is when you need to start worrying.