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.
In my IOS application, I have a NSDate* property that is marked as retain
When My application becomes active again, the properties value has been released.
Did I misunderstand how properties and memory management work, and how can I guard against this?
Its obvious that something is sending a release or dealloc message somewhere.
If I were you I would create a deep copy like:
NSItem *ref = [[NSItem alloc] initWithData: x];
As far as finding out what is happening to that item in question I suggest you use NSZombie as an env variable as step through the call stack to see where its getting released.
Best of luck!