On Aug 29, 2014, at 11:40 AM, Paul Miller <paul@fxtech.com> wrote:

On 8/29/2014 11:28 AM, Darrin Cardani wrote:

...

Paul,

Can you give us any more information? How are you sending the project to Compressor? How complex is the sequence? Does it happen if your plug-in isn’t applied?

Obviously Compressor is a different app and has different memory characteristics, but beyond that, it’s hard to do more than speculate. If you want to send us a project and a plug-in, we could try it out and see what we can find. You can probably run Compressor in the Leaks tool with Instruments and see if it gives you a common stack trace for where the leaked memory is coming from. If you do that, feel free to send me the results and I’ll take a look.

Darrin - I was going to try that, though I don't know how to use Compressor yet. When I render through Compressor, does Compressor actually do the rendering? ie. does it have the Motion effects engine built into it? Is there a way to send a project to Compressor, then quit Compressor and re-launch it from Instruments, and have it pick up the rendering? Or can I "attach" Instruments to it like I can with the debugger?

I don’t remember off the top of my head if Compressor renders things directly or has a daemon which does that. I will look into it. You can definitely attach instruments to a running process, though. There’s a popup near the top of the window next to the start/stop buttons that lists current processes and allows you to attach to one. Darrin _______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com