Does every thread have to have its own pool? I am writing an iPhone app which uses threads. If I do not put a pool on a thread it complains abut leaking.
What I wanted to do was to store some object which outlives the thread. How can I do it?
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.
No, every
NSThreadhas its ownNSRunLoop, but not its ownNSAutoreleasePool. Thus you have to create one and if you are performing a large operation or a operation that needs a lot of time, you really shoulddrainthe pool from time to time to keep your memory footprint low.Object storage isn’t bound to a thread at all, you can access every object from every thread you want, but it is possible that the accessor to the object isn’t threadsafe and thus kills your app. However, this depends on your app and your code and not on threads.