When you send an object a autorelease message, its retain count is decremented by 1 at some stage in the future. The object is added to an autorelease pool on the current thread. The main thread loop creates an autorelease pool at the beginning of the function, and release it at the end. This establishes a pool for the lifetime of the task. However, this also means that any autoreleased objects created during the lifetime of the task are not disposed of until the task completes. This may lead to the taskʼs memory footprint increasing unnecessarily. You can also consider creating pools with a narrower scope or use NSOperationQueue with itʼs own autorelease pool. (Also important – You only release or autorelease objects you own.)
-
Migrating Away from Threads The idea is that you eliminate work on your part, since the paradigm fits MOST code more easily. It reduces ...
-
Yes, the object is retained. It creates a timer that calls a selector on the current threads run loop. It may not be 100% precise time-wise...
-
Providing Counts for the Picker View – numberOfComponentsInPickerView: – pickerView:numberOfRowsInComponent: Delegate - Setting the Dim...