• 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: CIImage (TIFFRepresentation) memory leak
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CIImage (TIFFRepresentation) memory leak


  • Subject: Re: CIImage (TIFFRepresentation) memory leak
  • From: Brady Duga <email@hidden>
  • Date: Mon, 10 Mar 2008 13:34:06 -0700


On Mar 10, 2008, at 1:21 PM, Gary L. Wade wrote:

If all the code you're using is present, it looks to me like you're not releasing the object pointed at by image; the object returned by imageWithData is not an auto-released object.

It's not? Why not? I thought convenience methods like that did not transfer ownership to the caller. Isn't the convention that the method should say alloc, new or copy to signify the granting of ownership?


--Brady
_______________________________________________

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: 
 >Re: CIImage (TIFFRepresentation) memory leak (From: "Gary L. Wade" <email@hidden>)

  • Prev by Date: Re: No track index in iTunes SB?
  • Next by Date: Re: Core Animation Choppyness
  • Previous by thread: Re: CIImage (TIFFRepresentation) memory leak
  • Next by thread: Re: CIImage (TIFFRepresentation) memory leak
  • Index(es):
    • Date
    • Thread