site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Darrin On Oct 2, 2008, at 3:06 PM, Stonewall Ballard wrote: Darrin, - Stoney On Oct 2, 2008, at 1:13 PM, Darrin Cardani wrote: Jim, -- Darrin Cardani dcardani@apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... As long as you autorelease them like you say, that should work just fine. And it makes the memory management a lot easier! Great suggestion! I've been using an autorelease pool set up at the beginning of renderOutput: and autoreleasing any bitmaps I fetch during that method execution. Any reason why that's a bad idea? If you're never releasing the images the host application gives to you then you are leaking memory and possibly OpenGL textures and you will eventually crash. You do need to call [myImage release] explicitly on any images the host app gives to you. I recommend using them, and then releasing them in your render method, although you could also get them in your -frameSetup::: method and release them in -frameCleanup. This email sent to site_archiver@lists.apple.com