Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

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.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7946919
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 4, 20262026-06-04T01:17:03+00:00 2026-06-04T01:17:03+00:00

Do I still need to set IBOutlet properties to null in viewDidUnload with ARC?

  • 0

Do I still need to set IBOutlet properties to null in viewDidUnload with ARC?

Because it still generates the following comment:

// Release any retained subviews of the main view.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-04T01:17:04+00:00Added an answer on June 4, 2026 at 1:17 am

    For IBOutlets marked as strong you still do want to nil them out in viewDidUnload.

    Why:

    When you receive a low memory notification any views not currently visible may unload themselves (calling viewDidUnload) to save memory. By nilling out your outlets you are giving up ownership and letting them be released. When the view is loaded again (when it is shown again), the outlets will be setup again and viewDidLoad will be called.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

If I don't do any map/reduce jobs, still JobTracker/TaskTrackers need to be running for
If I already set SSL for my application server, do I still need to
Do we still need to bother with vcredist.exe when distributing windows native applications ?
I was wondering would I still need to use a basic game loop for
If I've overloaded operator+ and operator= do I still need to overload operator+= for
If I skip, do I still need to read the end element? reader.ReadStartElement(ENCODING); reader.Skip();
I'm a 80% ruby on rails developer, but still need to do some Access
Is this combination possible at all? If yes, will I still need to buy
This may be a stupid question to ask, but still I need to know
I need help with a specific LINQ query (I still suck at em'!) Background

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.