When I analyze my code it shows up a potential leak when I assign a Core Data String-attribute to a UILabel
cell.textLabel.text = prop.new_value;
Running the App with Instrument and Leaks doesn’t show any problem.
Share
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.
When I analyze my code it shows up a potential leak when I assign a Core Data String-attribute to a UILabel
cell.textLabel.text = prop.new_value;
Running the App with Instrument and Leaks doesn’t show any problem.
The static analyzer understands certain cocoa conventions such as methods beginning with “new” returning a retained object pointer.
I would suggesting changing “
new_value” inprop.new_valueto something different.Source: http://clang.llvm.org/docs/AutomaticReferenceCounting.html#objects.operands.retained_returns