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 6056585
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T08:23:36+00:00 2026-05-23T08:23:36+00:00

Suppose I have 2 views. In the first view, I allocate memory to displaying

  • 0

Suppose I have 2 views. In the first view, I allocate memory to displaying many UI components such as an UILabel, UIImages, etc.

Suppose the user navigates to the next view (via UINavigationController)

Is it OK to deallocate memory assigned to displaying UI components in the first view and then initialize them again once the user goes back to the first view (in viewFirstLoad or the appropriate function)?

It seems to me if you don’t do this, then memory will keep on increasing the longer the user uses your app in that particular session.

Is this not allowed? frowned upon? impossible?

  • 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-05-23T08:23:36+00:00Added an answer on May 23, 2026 at 8:23 am

    It is perfectly normal and in fact, that functionality is built in standard UIViewController – when controller is not displayed its view may be released from memory and you can release all its subviews (e.g. retained through IBOutlet references) in controller’s -viewDidUnload method.

    When controller needs to display again it reloads its view again.

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

Sidebar

Related Questions

Suppose I'm implementing an MVP pattern and I have a view interface as such:
Suppose you have a Django view that has two functions: The first function renders
Suppose I have a list of tickets. When the user first goes to the
Suppose I have a scroll view in a view & a scroll view's size
There's no strongly typed View() method to return an ActionResult. So, suppose I have
Why is using '*' to build a view bad ? Suppose that you have
Suppose I have a view with the following control (DataContext is properly set to
Suppose you have data for which a normalized view would be something like ID
Suppose you have three tiers (with namespaces): User interface ( App.UI ) - calls
First, i would to apologize for my bad english. Suppose i have function in

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.