(iphone) UIImage memory management problem.

最新推荐文章于 2025-08-09 19:02:03 发布

转载最新推荐文章于 2025-08-09 19:02:03 发布 · 762 阅读

文章标签：

#iphone #leak #search #buffer #kill #ios

iPhone开发专栏收录该内容

202 篇文章

订阅专栏

讨论了如何在iOS应用中有效管理UIImage内存，指出 Instruments 工具不考虑UIImage大小，而是通过计算活动UIImage实例的数量来评估内存使用情况。建议通过跟踪UIImage数量来定位内存泄漏，并提供了在频繁创建销毁UIImage时保持应用性能的方法。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

问题：

I'm having trouble with UIImage memory management.
(iphone) my app gets memory warning when instruments shows "all allocations" only 7mb ?

Essentially, I create/destroy UIImage many times.
Even if I make memory consumption at a time low using local NSAutoreleasePool, iphone/ipad device keeps complaining about memory usage.

I'm thinking, I should allocate UIImage to specific memory buffer(or pool of buffer) which I can designate to.
Is this possible?

Or any other suggestion on how to create/destroy UIImages many times without upsetting iOS would be much appreciated.

Thank you.

回答：

It is not a well known fact, but Instruments does not consider the size of UIImages within the allocated memory. You could be leaking 100Mb of UIImages and the allocated memory would not tell the story. What does tell the story is the number of live UIImage instances at a given moment.

In the Allocations instrument, using the top-right search box, search for "Image". Then look for the column labeled #linving in UIImage. That number is the number of UIImage objects. That is a better compass in to figuring out where are your UIImages going. If at some point you have more objects than what you expect, and thease UImages are not going away you have a UIImage leak in your hands. An UIImage leak will kill your app real fast.