I see a lot of people saying
imageNamed is bad but equal numbers of people saying the performance is good - especially when rendering
UITableView s. See this SO question for example or this article on iPhoneDeveloperTips.com
imageNamed method used to leak so it was best avoided but has been fixed in recent releases. I'd like to understand the caching algorithm better in order to make a reasoned decision about where I can trust the system to cache my images and where I need to go the extra mile and do it myself. My current basic understanding is that it's a simple
UIImages referenced by filename. It gets bigger and when memory runs out it gets a lot smaller.
For example, does anyone know for sure that the image cache behind
imageNamed does not respond to
didReceiveMemoryWarning ? It seems unlikely that Apple would not do this.
If you have any insight into the caching algorithm, please post it here.