Navigation Controller problems

[thomas02]

Hi, I have an app that has alot of view and when I navigate to a view with an image on it the memory goes from 2mbs used to 15mbs used and then return to the previous view the memory stays at 15. I have released the images on the view and the memory still doesnt release. Please help.

[BrianSlick]

If you simulate a memory warning, does it go back down?

[thomas02]

Originally Posted by BrianSlick

If you simulate a memory warning, does it go back down?

No it doesnt

[BrianSlick]

Post some code then.

[thomas02]

Im new a development and dont know what to post sorry.

[BrianSlick]

Well, you think the problem is related to images, then post code related to images. Where you create them, how you use them, how you destroy them, etc.

[thomas02]

Originally Posted by BrianSlick

Well, you think the problem is related to images, then post code related to images. Where you create them, how you use them, how you destroy them, etc.

in my .h

@property(nonatomic,retain)IBOutlet UIImageView *fast1;
@property(nonatomic,retain)IBOutlet UIImageView *fast2;
in the .m

- (void)viewDidDisappearBOOL)animated {
[super viewDidDisappear:animated];
NSLog(@"release");
[fast1 removeFromSuperview];
[fast2 removeFromSuperview];
[texts removeFromSuperview];
}


- (void)dealloc {
NSLog(@"Releasing");
[fast1 release];
[fast2 release];
[texts release];
[super dealloc];
}
i just add them in IB and attach the outlet so I can remove them and release the mem.

[BrianSlick]

Do you see the "Releasing" log?

Removing from superview isn't necessary, btw. If that is the only reason you have the outlets, don't bother.

[thomas02]

Originally Posted by BrianSlick

Do you see the "Releasing" log?

Removing from superview isn't necessary, btw. If that is the only reason you have the outlets, don't bother.

In the log I see that they are releasing. So I can still release them if I dont have and outlet for them?

[BrianSlick]

You don't need to. The view will release the imageviews - which will in turn release the images - when the view controller goes away.

I'm not seeing any errors in the code here, so as long as you are certain that the view controller is dying, I wouldn't worry about it. You're probably just seeing the image cache.

[thomas02]

Originally Posted by BrianSlick

You don't need to. The view will release the imageviews - which will in turn release the images - when the view controller goes away.

I'm not seeing any errors in the code here, so as long as you are certain that the view controller is dying, I wouldn't worry about it. You're probably just seeing the image cache.

How do I tell if the view controller is dying? When I navigate back from the view with the images the memory used goes up.

[BrianSlick]

If you are seeing that log in the dealloc method, then the view controller is dying.

[thomas02]

Originally Posted by BrianSlick

If you are seeing that log in the dealloc method, then the view controller is dying.

ok thanks

[BrianSlick]

If you go forward and back a bunch of times, does the memory keep growing, or does it stay around 15?

[thomas02]

I just ran it through again and the log showed a level 1 memory warning.

[thomas02]

Originally Posted by BrianSlick

If you go forward and back a bunch of times, does the memory keep growing, or does it stay around 15?

It grows and shrinks about .2 mbs every time

[BrianSlick]

That doesn't answer my question.

Edit: Ok, if you were leaking, then you would continue to grow and grow. If it stays the same, you aren't leaking.

[thomas02]

when running it in instruments, the leaked bytes just keeps growing and the memory used keeps growing and growing.

[BrianSlick]

Get your story straight. Just a minute ago you said it would grow and shrink.

So since you are using Instruments, you should be able to figure out what kind of objects are leaking.

[thomas02]

Originally Posted by BrianSlick

Get your story straight. Just a minute ago you said it would grow and shrink.

So since you are using Instruments, you should be able to figure out what kind of objects are leaking.

It tells me the only leak discovered is an array.

[BrianSlick]

Ok, are you using any arrays in this view controller?

[thomas02]

Originally Posted by BrianSlick

Ok, are you using any arrays in this view controller?

No, but I have many in the rest of the app.

[BrianSlick]

Start tracking those down, then.

[thomas02]

Originally Posted by BrianSlick

Start tracking those down, then.

Ok

[thomas02]

I have released all of the arrays and it still gives me warnings for them leaking memory and now the app is really slow and then it crashes.