Skip to main content

removeFromSuperview and release memory management



I have a MBProgressHUD that I allocate as follows:







self.progressHUD_ = [[[MBProgressHUD alloc] initWithView:self.view] autorelease];







if I call removeFromSuperview then would I have to call progressHUD release again? Also if I declare a property with something like this:







NSString * title_;



@property (nonatomic, retain) NSString * title_;







then it is guaranteed that in my dealloc I should have a release on title right?


Comments

  1. No, you don't have to release it again. Views retain their subviews and release them again automatically when you call removeFromSuperview. As long as the view has been autoreleased when you attach it to the view, it will be released when it is removed from the view.

    I didn't quite understand your second question, but yes, you have to release any properties of type "retain" or "copy" in your dealloc statement. You have to write those release statements manually, they aren't added automatically (unless you are using ARC of course, which I strongly recommend).

    ReplyDelete
  2. How is your progressHUD_ property defined? (btw, the ivar should have a trailing underscore, but not the property name).

    In case it is defined as (retain, whatever), you will have to release it again:


    When you create it, its retainCount is +1.
    When you assign it to your property, its retainCount will be increased by one.
    When you add it as a subview to the parent view, its retainCount will be increased by one.
    At some point, autorelease will eventually decrease it by 1, but the view and the property still hold on to it.


    So you'll have to either set your property to nil or call release on the ivar in your dealloc method.

    Also, you probably want to use copy instead of retain when defining an NSString property. And yes: you'll have to release it either way.

    ReplyDelete

Post a Comment

Popular posts from this blog

Slow Android emulator

I have a 2.67 GHz Celeron processor, 1.21 GB of RAM on a x86 Windows XP Professional machine. My understanding is that the Android emulator should start fairly quickly on such a machine, but for me it does not. I have followed all instructions in setting up the IDE, SDKs, JDKs and such and have had some success in staring the emulator quickly but is very particulary. How can I, if possible, fix this problem?

CCNA 1 Final Exam 2011 latest (hot hot hot)

  Hi! I have been posted content of ccna1 final exam (latest and only question.) I will post the answer and insert image on sunday. If you care, please subscribe your email an become a first person have full test content. Subcribe now  Some question  have not content because this question have images content. So that can you wait for me? SUNDAY 1. A user sees the command prompt: Router(config-if)# . What task can be performed at this mode? Reload the device. Perform basic tests. Configure individual interfaces. Configure individual terminal lines. 2. Refer to the exhibit. Host A attempts to establish a TCP/IP session with host C. During this attempt, a frame was captured with the source MAC address 0050.7320.D632 and the destination MAC address 0030.8517.44C4. The packet inside the captured frame has an IP source address 192.168.7.5, and the destination IP address is 192.168.219.24. At which point in the network was this packet captured? leaving host A leaving ATL leaving...