Home/ Questions/Q 8426953
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-10T04:40:11+00:00

I have a MyViewController, it’s based on UIViewController, and I used it like the

  • 0

I have a MyViewController, it’s based on UIViewController, and I used it like the following code:

MyViewController *nextViewController = [[MyViewController alloc] init];
[self.navigationController pushViewController:nextViewController animated:YES];
[nextViewController release];

And in the MyViewController, with a user event, have the following code:

[self.navigationController popViewControllerAnimated:YES];

Now, I find that, the MyViewController’s dealloc don’t be called, but, when I switch the App to background, for example, pass the home button, the dealloc method has been called! This a big problem! There will be got a lot of MyViewController wouldn’t be release, when user go to a MyViewController, and go back, again and again, and just, the lots of memory could be release only when the App goto background.

So, can anyone help me about this, thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The obvious reason is that something is retaining your viewController. You will have to look closely at your code. Do you do anything that in your class that uses delegates, since they sometimes retain the delegate. NSURLConnection will retain your class, and so does NSTimer. You can scatter code in you class and log your class’s retain count, and try to find out where. In the code you showed so far the retain could should just be 1, since the class is only retained by the navigation controller.

    Also, before you pop your view, get a reference to it, pop it with NO animation, and then send it some message that has it report the retain count (this would be some new method you write). That new method could also log other things, like whether it has any timers going, NSURLConnections, etc.

    • 0