Here's a little more light on a similar matter...
I've just stumbled across a memory leak when outputting humble strings from JavaScript patches. There's nothing special about this, but each time the JS executes, it outputs a string:
JS String leak.qtz
Description: application/quartzcomposer
If I perform an ObjectAlloc trace on this, it appears that the strings are never released, not even when the document is closed in QC.
Can anyone else confirm this is the case, and that I'm reading my ObjectAlloc traces correctly?
Also, instead of assuming this is fixed in 10.6, what is the possibility issues like this will be fixed in 10.5? We make heavy use of JavaScript patches to generate strings in many of our projects, and knowing there are leaks like this is a bit worrying.
I've submitted this as rdar://7064842 On 12 Jul 2009, at 12:28, Chris Wood wrote:
I had exactly the same leak issue (when loading images regularly) but much more severely ( 1mb+ images, and lots of them). I can't remember exactly how I fixed it unfortunately, but it was just a case of changing what I was doing in QC. It was likely discussed on the list here, so a bit of searching might turn up some answers. Or perhaps somebody else has a better memory?Chris On 12 Jul 2009, at 12:17, Adrian Ward wrote:Try using Instruments.app and it's ObjectAlloc tool to see what is slowly taking up memory. By watching the allocations over a few minutes it should be easy to see what is leaking.It'll usually appear to be a lower-level object (NSString, CFDictionary etc) but by using Outline View and the Extended Detail View and selecting the object at fault you can see the heaviest stack trace of calls that lead up to it, some of which will pass through Quartz Composer internals (or perhaps via a plugin you're using), giving a clue as to which patch is taking up memory.We had a similar memory leak with the built in movie loader that was more dramatic - hundreds of megabytes within half an hour - and we managed to find a work around using the above technique.Caveat lector: there may be beter ways of doing this. A Jedi Cocoa developer may give better advice.Ade. On 12 Jul 2009, at 02:36, Adrian Lo <[email protected]> wrote:Hello,There's something that I had noticed in regards to the memory usage of Quartz Composer. I've got this composition that reads in a XML file (the XML Downloader patch) and 3 images (via the Image Downloader patch). This loops every 8 seconds or so. After leaving it to run for around 10 hours, I noticed that the memory usage has gone from 30mb+ to 185mb now.Is there some sort of memory leak issues to watch out for when using some patches? The files downloaded are pretty small still. The XML file is just around 380bytes in size, and the images are around 3.5k/b or so in size.Would really appreciate some feedback on this, and thanks in advance.Regards, Adrian _______________________________________________ Do not post admin requests to the list. They will be ignored.Quartzcomposer-dev mailing list ([email protected] )Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/adrian%40clayinteractive.co.uk This email sent to [email protected]_______________________________________________ Do not post admin requests to the list. They will be ignored.Quartzcomposer-dev mailing list ([email protected] )Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/psonice%40gmail.com This email sent to [email protected]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [email protected]
