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: 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?
You should maybe use Leaks instead of ObjectAlloc, but *I am also able to verify this*. Looks like the leak originates in JavaScriptCore (which is maybe updated when WebKit/Safari is), so it might not be QCs fault (though it's difficult to tell -- it could be QC mishandling returned results.
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.
Hopefully a safari update will address it (if it's actually JSC's fault), or maybe 10.5.8 (if it's QC's fault).
-- [ christopher wright ] [email protected] http://kineme.net/
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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]
