• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
questions on memory issues
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

questions on memory issues


  • Subject: questions on memory issues
  • From: John Michael Zorko <email@hidden>
  • Date: Tue, 10 Nov 2009 13:41:37 -0800


Hello, all ...

Firstly, I very much appreciate the help i've received here -- thank you very much :-)

I've a debugging question. I've an issue that manifests as what appears to be a dangling pointer. I've a view that is loaded, and all is fine. This is OS 2.2.1. My understanding is that under OS 2.x, the view controller only releases it's view when the view controller is released. However, if I put a breakpoint on my view controller's - loadView method, it's called again sometime later (and it's view property is now something completely different, pointing to an NSArray, NSOperation or something else), without the view controller's -dealloc method being called beforehand. I would think that if the view controller had to be released, say because of a memory warning, that its' -dealloc method would be called. I don't know why it's not ...

In OS 3.x, I can just be sure to catch the viewDidUnload delegate method and set the view to nil, and make sure I recreate it in loadView, but I would like to target OS 2.2.1 if at all possible.

Regards,

John

Falling You - exploring the beauty of voice and sound
http://www.fallingyou.com



_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Prev by Date: Re: CALayer subclass allocation problem
  • Next by Date: Localization of System Preferences Pane
  • Previous by thread: Re: 10.6.2 Core Data Incompatibility
  • Next by thread: Re: questions on memory issues
  • Index(es):
    • Date
    • Thread