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

  • Home
  • SEARCH
  • 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 8732875
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 13, 20262026-06-13T09:31:30+00:00 2026-06-13T09:31:30+00:00

I am subclassing UIViewController to prevent code repetition of my ‘masterButtons’ and sets of

  • 0

I am subclassing UIViewController to prevent code repetition of my ‘masterButtons’ and sets of ‘subButtons’.

It all appeared to be working beautifully until I realised that after about 1200 page changes – navigating between just 3 blank pages (just the buttons and a few other objects showing) the app will always crash!

Instruments (+ testing on a device) does not show any memory leaks, but does show hundreds of instances of these button objects existing! (‘Created & Still Living’ filter selected.)
Also, viewDidUnload / didReceiveMemoryWarning are never called, from any of the ViewControllers!

I have not had these problems on other pages in my app (where UIViewController is NOT subclassed).

So it appears the ViewController’s contents are being re-created, and any previously created are not being deleted.
Are there any common pitfalls of subclassing UIViewController that might be causing this? Is there something I could be missing?

Advice would be greatly appreciated. (I feel like throwing my mac out of the window with this problem!)

Top_ViewController      (contains 'MasterButtons')
       v
Area1_ViewController    (subclass of TOP_ViewController) (contains 'subButtons', and  a few texts fields etc.)
       v
aPage_ViewController    (subclass of Area1_ViewController)  (currently blank page)

(Using ARC and storyboards. The storyboard View Controllers have a respective ‘aPage_ViewController’ as their class.)

  • 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-13T09:31:31+00:00Added an answer on June 13, 2026 at 9:31 am

    If you created your storyboard in a loop fashion it might happen that you create new viewControllers all the time. Each segue transition is creating new viewController thus there might be no memory leak but your memory will be consumed.

    You should be using either UITabBarController or UINavigationController to move back and forth and never create loops.

    Moreover viewDidUnload is deprecated in iOS6, perhaps you ignored warning?

    EDIT:

    Try something like this:

    -(void)tab1_IsPressed:(UIButton *)paramSender{
        Top_ViewController *target_VC = (Top_ViewController*)[self.storyboard instantiateViewControllerWithIdentifier:@"page_1"];
        [self.navigationController popViewControllerAnimated:NO];
        [self.navigationController pushViewController:target_VC animated:NO];
    }
    -(void)tab2_IsPressed:(UIButton *)paramSender{
        Top_ViewController *target_VC = (Top_ViewController*)[self.storyboard instantiateViewControllerWithIdentifier:@"page_2"];
        [self.navigationController popViewControllerAnimated:NO];
        [self.navigationController pushViewController:target_VC animated:NO];
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

When subclassing UIView , I usually place all my initialisation and layout code in
I am subclassing UITextView, and i got it working, but i also want to
If one can prevent subclassing by declaring private constructor in the base class, why
I am always subclassing UITableViewCell's and drawing them in code. Is there a good
I'm writing my own SplitViewController from scratch (i.e. by subclassing UIViewController and not UISplitViewController
I'm creating a custom popover for a UIPopoverController by subclassing UIViewController to manage the
-Using ARC -I have 5 separate view controllers all subclassing a class I made
When subclassing, I tend to give all my properties the attributes (nonatomic, strong), except
When subclassing a base class, an inherited method is not working as expected. I've
In some code requiring subclassing of inner traits/classes I'm having trouble successfully implementing an

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.