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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 1, 20262026-06-01T02:27:26+00:00 2026-06-01T02:27:26+00:00

My object is staying alive and I’m not sure why . I’m sure the

  • 0

My object is staying alive and I’m not sure why. I’m sure the reason(s) are obvious, but I’m too green to see them. I’m watching the allocations in instruments and the memory is never released..

My header file is attached. How SHOULD I be taking care of business here? Thanks for advice/suggestions.

FYI – This is for ios5 developed with xcode 4.3. ARC is enabled.

** EDITS / ADDITIONS **

  • This UIView is what is staying alive even after I switch to a completely different View Controller (via storyboard segue). I suspect it’s a strong reference or a reference that can’t be let go of?

  • As far as I can tell, this view is never released.

  • I’m tracking allocations with intruments new->allocations => choose target->ios 5.1 device => record. And just watching the graph as I touch around.


#import <UIKit/UIKit.h>
#import "ValidatedTextField.h"

@interface LoginView : UIView {
    NSString *loginEmail;
    NSString *loginPassword;
}

@property (nonatomic, weak) IBOutlet UIView *loginView1;
@property (nonatomic, weak) IBOutlet UIView *loginView2;
@property (nonatomic, weak) IBOutlet UIView *loginView3;
@property (nonatomic, weak) IBOutlet UIView *loginView4;

@property (nonatomic, weak) IBOutlet UIView *recoverView1;
@property (nonatomic, weak) IBOutlet UIView *recoverView2;

@property (nonatomic, weak) IBOutlet UIScrollView *loginSV;
@property (nonatomic, weak) IBOutlet UIScrollView *recoverSV;

@property (nonatomic, weak) IBOutlet ValidatedTextField *signInEmailInput;
@property (nonatomic, weak) IBOutlet ValidatedTextField *signInPassInput;
@property (nonatomic, weak) IBOutlet ValidatedTextField *createEmailInput;
@property (nonatomic, weak) IBOutlet ValidatedTextField *createFirstNameInput;
@property (nonatomic, weak) IBOutlet ValidatedTextField *createLastNameInput;
@property (nonatomic, weak) IBOutlet ValidatedTextField *passInput;
@property (nonatomic, weak) IBOutlet ValidatedTextField *rePassInput;
@property (nonatomic, weak) IBOutlet ValidatedTextField *recoverIDInput;

@property (nonatomic, weak) IBOutlet UIButton *signInBtn;
@property (nonatomic, weak) IBOutlet UIButton *forgotPassBtn;
@property (nonatomic, weak) IBOutlet UIButton *createAccountBtn;
@property (nonatomic, weak) IBOutlet UIButton *createBackBtn;
@property (nonatomic, weak) IBOutlet UIButton *createContinueBtn;
@property (nonatomic, weak) IBOutlet UIButton *passBackBtn;
@property (nonatomic, weak) IBOutlet UIButton *passContinueBtn;
@property (nonatomic, weak) IBOutlet UIButton *sumBackBtn;
@property (nonatomic, weak) IBOutlet UIButton *sumSubmitBtn;
@property (nonatomic, weak) IBOutlet UIButton *recoverBackBtn;
@property (nonatomic, weak) IBOutlet UIButton *recoverPassBtn;
@property (nonatomic, weak) IBOutlet UIButton *returnToSignInBtn;

@property (nonatomic, weak) IBOutlet UILabel *signInEmailError;
@property (nonatomic, weak) IBOutlet UILabel *createEmailError;
@property (nonatomic, weak) IBOutlet UILabel *passwordError;
@property (nonatomic, weak) IBOutlet UILabel *sumEmail;
@property (nonatomic, weak) IBOutlet UILabel *sumFirstName;
@property (nonatomic, weak) IBOutlet UILabel *sumLastName;
@property (nonatomic, weak) IBOutlet UILabel *sumPassword;
@property (nonatomic, weak) IBOutlet UILabel *emailedToTxt;

-(IBAction)signInTUI:(id)sender;
-(IBAction)forgotPassTUI:(id)sender;
-(IBAction)createAccountTUI:(id)sender;
-(IBAction)createBackTUI:(id)sender;
-(IBAction)createContinueTUI:(id)sender;
-(IBAction)passBackTUI:(id)sender;
-(IBAction)passContinueTUI:(id)sender;
-(IBAction)sumBackTUI:(id)sender;
-(IBAction)sumSubmitTUI:(id)sender;
-(IBAction)recoverBackTUI:(id)sender;
-(IBAction)recoverPassTUI:(id)sender;
-(IBAction)returnToSignInTUI:(id)sender;

@end
  • 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-01T02:27:28+00:00Added an answer on June 1, 2026 at 2:27 am

    This UIView is what is staying alive even after I switch to a completely different View Controller (via storyboard segue). I suspect it’s a strong reference or a reference that can’t be let go of?

    I’m assuming here you mean that you’re segue-ing it as a push onto a navigation controller stack or you’re presenting modally or something:

    It shouldn’t necessarily be deallocated when you go to a new view controller. The original view controller, hence its view and hence your custom view will still stay alive until UIKit decides to kill it because memory is getting low. At that point your view controller object would still stay alive, but its view would be unloaded and you’d get the viewDidUnload. Only when you remove that view controller completely from any navigation controller / tab controller / dismiss it if it modal, will it be completely destroyed.

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

Sidebar

Related Questions

Object reference not set to an instance of an object. using System; using System.Collections.Generic;
object_getIvar(id object, Ivar ivar) reads the values of iVArs properly but fails on a
I am getting error saying: Object reference not set to an instance of an
I have a (java) class with about 10 attributes, many of them potentially staying
This is a strange issue and not sure what is going on. I am
I'm sure this question has been asked over and over again, but for some
I am trying to pop a RadWindow.. but its giving an error saying object
Object slicing is some thing that object looses some of its attributes or functions
Object doesn't support this property or method It's this line. pthumb = $(#pthumb).attr(src); Does
object(stdClass)[1] public 'inbox' => array 0 => object(stdClass)[2] public 'from' => string '55512351' (length=8)

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.