site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Hi Micah, Final Cut is still a 32-bit app, so we have about a 4GB address limit. - Paul On Aug 26, 2008, at 5:35 PM, Micah Sharp wrote: Thanks, Micah _______________________________________________ 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/pschneider%40apple.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... we had this problem in previous versions of Final Cut, but it was fixed in 6.0.2 (I believe). If you call [yourImage release], the memory for the image should be freed up right then and there. Hi, I recall a while back it was confirmed that when getting temporal frames inside the render method of an FxPlug, the images are not released until the end of the render method, causing crashing eventually if you get too many frames in a row. We do have a plug-in that needs to do this on a lot of frames, and we are seeing crashing with HD sized images, and attempts to get anything over about 10 seconds worth of frames. The machine had 5 GB of RAM, and I think the un-released memory must be about 2.8GB or so. What is the threshold then? We have users with 16GB of memory on their machines seeing the same problem. Is it just a fixed ceiling, or is it related to memory on the user's machine? Is it truly running out of memory and just crashing (pretty sure we check for a null result, etc)? Final question, is there a bug filed against this. Nice problem to not have... This email sent to pschneider@apple.com This email sent to site_archiver@lists.apple.com