I modified the example to just reload the composition into the qcview every 
second.  Looking at the output of "top", it does seem to be growing as 
described by Instruments.app - I'm no memory expert but I can see the numbers 
going up by about 1 MB every 20 minutes or so.  To me, that seems worrisome 
considering all the app is doing is loading a qtz into a view every second.  
Assuming I trust what Instruments and top are telling me, what's the deal? 
Surely it's possible to make an application that loads/reloads compositions 
without it growing in size to infinity?

rob

On Jan 20, 2012, at 8:00 PM, George Toledo wrote:

> Have you tried profiling apps like Safari, iTunes, etc. as a reference for 
> what one sees in Instruments.app as "leaks"? Might be worth looking at.
> 
> On Fri, Jan 20, 2012 at 5:13 PM, Rob Duarte <ra...@rahji.com> wrote:
> Hi,
> 
> I'm trying to load a sequence of compositions into a QCView and I'm seeing 
> consistent leaking when I run the application through Instruments.
> 
> In my specific application, I'm loading several compositions from qtz files 
> into an NSArray of QCCompositions at the start. Then I'm loading those 
> QCCompositions from the array into the QCView whenever the user presses a 
> button in the UI.
> 
> However, in trying to pare this application down to the bare minimum for 
> troubleshooting this, I got to the point where I was just loading the same 
> qtz every time a button was pressed and I see the same leaking.
> 
> In fact, if I just create a new project in XCode using the "Quartz Composer 
> Application" (which appears to leak without any modifications)... then 
> replace the contents of the changeColorToBlue method with code to just reload 
> the same composition into the QCView:
> 
> if (![qcView loadCompositionFromFile:[[NSBundle mainBundle] 
> pathForResource:@"Introduction" ofType:@"qtz"]]) NSLog(@"Could not load 
> composition");
> 
> ... you can see that every time you click the button in the UI, the same 
> leaks are added to the pile.
> 
> I'm not sure how to proceed - at the simplest, I need an application that can 
> cycle through several compositions and continue running for many hours but 
> even that doesn't seem possible right now.  Granted, the leaks are not huge 
> but I'd expect this to work without any leaks.  The simple modification to 
> the template that I just described leaks around .5K every time you load a 
> composition into the view.
> 
> Is there something I'm missing?
> 
> Thanks for any help,
> Rob
> 
> 
> 
>  _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Quartzcomposer-dev mailing list      (Quartzcomposer-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/quartzcomposer-dev/gtoledo3%40gmail.com
> 
> This email sent to gtole...@gmail.com
> 

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list      (Quartzcomposer-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to