Re: Continuously running daemon process CFConstantStringRefs build up over time
Re: Continuously running daemon process CFConstantStringRefs build up over time
- Subject: Re: Continuously running daemon process CFConstantStringRefs build up over time
- From: Dave Keck <email@hidden>
- Date: Fri, 1 Oct 2010 18:57:40 -0400
> CFStringRef hexStringRef = CFStringCreateWithFormat( NULL, NULL, CFSTR("%x"), versionValue ); <----- Instruments is hi-lighting this line as an allocation.
It sounds like you found the cause of your persisting string objects
so the details of CFSTR is irrelevant, but to clarify anyway: the
result of CFStringCreateWithFormat() is of course an allocation as
Instruments reported, but the format string that you supplied
CFStringCreateWithFormat() – that is, the CFString whose value is "%x"
– exists statically within your executable (in the __DATA/__cfstring
segment/section) and is therefore not an allocation.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden