• 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
Re: Weird release problem on iPhone code
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Weird release problem on iPhone code


  • Subject: Re: Weird release problem on iPhone code
  • From: Jens Alfke <email@hidden>
  • Date: Thu, 18 Mar 2010 20:48:04 -0700

On Mar 18, 2010, at 8:43 PM, William Squires wrote:

>  If I uncomment any of the object releases above, the app crashes in the simulator, and all the call-stack items are gray (non-user code). But if I don't release them, they'll leak memory, won't they, since iPhone OS doesn't have GC?

No. You don’t own any references to those objects, because you didn’t get them from methods like ‘alloc’, ‘retain’ or ‘copy’. You should reread the memory management guidelines…

—Jens_______________________________________________

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

References: 
 >Weird release problem on iPhone code (From: William Squires <email@hidden>)

  • Prev by Date: Weird release problem on iPhone code
  • Next by Date: Re: Weird release problem on iPhone code
  • Previous by thread: Weird release problem on iPhone code
  • Next by thread: Re: Weird release problem on iPhone code
  • Index(es):
    • Date
    • Thread