Take the 2-minute tour ×  I'm working on a project that requires
extreme care with memory. I ran the simulation on instruments
and it shows the next leak:  Leaked Object: NSCFString Size: 80
Bytes Responsible Library: Foundation Responsible Frame:
NSPlaceHolderString  I've searched all over my code and I'm not
explicitly creating a NSCFString.  Thanks in advance.
share|improve this question add comment  1 Answer  up vote 6
down vote accepted  NSCFString is the internal subclass that's
used for most NSStrings. You're leaking an NSString. It might
not even be something you created — you might be retaining a
string and not releasing it later.  share|improve this answer
add comment  Your Answer