Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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.
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.