• 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: CoreImage: Newbie can't find memory leak [SOLVED
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CoreImage: Newbie can't find memory leak [SOLVED


  • Subject: Re: CoreImage: Newbie can't find memory leak [SOLVED
  • From: Chris Lewis <email@hidden>
  • Date: Wed, 15 Feb 2006 02:22:16 +0000

> You did not allocate aImage or overlayImage IN THIS METHOD.
> Therefore you should not release or autorlease aImage or overlayImage
> IN THIS METHOD.

You know, that was exactly why I didn't do it in the first place. It
felt like a bad idea at the time :)

I got so excited I'd fixed it (it's seriously been about 8 hours of
screwing around, until it all finally clicked when I used
OmniObjectMeter, and really started *understanding*) I wanted to stop
other people on the list worrying about it :) The releases seemed
coupled to the setValue:, hence why I tried it there.

You're right Erik, I'll track back and find the origins of these
mystical images, and send them a release there.

Thanks for your help!
Chris
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: CoreImage: Newbie can't find memory leak [SOLVED
      • From: Scott Ellsworth <email@hidden>
References: 
 >Re: CoreImage: Newbie can't find memory leak [SOLVED (From: Erik Buck <email@hidden>)

  • Prev by Date: Re: NSDictionary convert into NSXMLDocument
  • Next by Date: NSConditionallySetsEditable
  • Previous by thread: Re: CoreImage: Newbie can't find memory leak [SOLVED
  • Next by thread: Re: CoreImage: Newbie can't find memory leak [SOLVED
  • Index(es):
    • Date
    • Thread