ansaurus

Question

Answer 1

+1 A:

Why would you want to set this to nil?

If it's a @property (retain) UILabel * labelDistance; (and synthesized), then just release it in dealloc. Or do you fiddle with that ivar around?

One note: your variable and property should begin with a lower letter "l".

Eiko 2010-06-20 22:14:30

Answer 2

+1 A:

Try:

[self.labelDistance release];
[self.distanceSlider release];

instead. Also, you shouldn't be releasing ivars in viewDidUnload, release them in dealloc. If the problem persists, run the static analyzer (Build menu >> Build and Analyze), it is generally good at finding memory related issues.

macatomy 2010-06-20 22:20:08

You should release IBOutlets in viewDidUnload. Because when the view is loaded again it will set them.

rickharrison 2010-06-21 00:43:33

Ah good point, I didn't realize they were IBOutlets.

macatomy 2010-06-21 01:09:18

@rickharrison - Although if they're properties constructed with the `retain` setter semantic, they'll be released in the synthesized setter when the new value is set. At which point, I think you'd run the risk of over-releasing them, if you did it in viewDidUnload too.

Dan Ray 2010-06-22 12:50:38

@Dan Ray - Well if you do self.iboutlet = nil in viewDidUnload than the memory will be reclaimed by the system. That also allows a safe call of resetting the outlet in viewDidLoad again.

rickharrison 2010-06-22 17:16:42

@rickharrison: I'm saying, I think that shouldn't be necessary, as long as the properties are of the "retain" style. Just assigning to that property a second time (as long as you use the @synthesized setter, possibly via dot notation) will release the previous content before it assigns.

Dan Ray 2010-06-23 12:02:37

ansaurus

tags:

views:

answers:

Getting EXC_BAD_ACCESS in viewdidunload

related questions