> 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?
Finding where the leaks are will help further isolate the problem (and help locate possible workarounds, if they exist). Providing your modified examples would be good, as would using MallocStackLogging=YES + leaks on the command line (to identify the calling backtrace of the leaked allocations). -- Christopher Wright christopher_wri...@apple.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
