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.
A selector have been scheduled to the frame rate, [self schedule:@selector(tick:)]; and it keep executing all time (since application run). thus it keep increasing the memory, that leads to degradation in performance. So can we keep releasing the memory while excuting the selector.
Schedule will only call the selector at frame rate interval, no memory is taken by this operation.
If you have memory which increases, maybe it’s because you have memory leak in your code inside the tick: method.
And no autoreleasepool is required because schedule lets the autorelease pool managed by the run loop to release autoreleased objects.