site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 Good time for me to step in here.. It would be REALLY REALLY REALLY be useful if the memory I allocate for my plugins are coordinated through FxPlug memory functions (instead of malloc). Our users run out of memory all the time. And not because there isn't memory, but because FCP doesn't seem to release some of it's cached images (or other memory) when we request memory via malloc. On 2/10/2011 4:57 PM, Peter Litwinowicz wrote: Probably a good time for me to add my request for this. Lately we've been getting crash reports from users working on very long sequences of Red footage. I've tested my code with Instruments and memory watchers and can't find any leaks, but I can't reproduce these occasional problems. I only allocate memory on a per-frame basis and then release it but if FCP is getting very aggressive with memory crashing and I need a couple of Red-sized buffers, could this be the same situation as Pete is in? _______________________________________________ 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... This email sent to site_archiver@lists.apple.com