分析仪器读数
泄漏：
None
ObjectAlloc：
Net Bytes: 4,332,512
# Net: 26,696
Overall Bytes: 103,769,552
# Overall: 738,987
活动监视器（MyApp）：
# Thread: 6
Real Memory: 63.65 MB
Virtual Memory: 209.45 MB
监视器显示的读数与活动监视器相同。 我不知道这些读物是好是坏。 活动监视器显示的内存非常可怕。 我应该担心吗？ 我可以以某种方式估计应用程序移动到设备后所使用的内存吗？ 实际运行时内存？ 谢谢。
Leaks:
None
ObjectAlloc:
Net Bytes: 4,332,512
# Net: 26,696
Overall Bytes: 103,769,552
# Overall: 738,987
Activity Monitor (MyApp):
# Thread: 6
Real Memory: 63.65 MB
Virtual Memory: 209.45 MB
Memory monitor showed same readings as Activity Monitor. I don't know whether these readings are good or bad. Memory indicated by Activity Monitor is horrifying. Should i be worried? Can i somehow estimate memory used by the application once its moved to the device. The real run time memory? Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
对象分配报告的内存使用情况并不是很权威，至少根据我的经验是这样。 真正的问题是内存监视器报告的实际内存消耗，请参阅 我关于 iPhone 内存的问题消费。 你的数字似乎是在模拟器中测量的，这样的测量毫无价值。 您必须在设备上进行测量。
Memory usage as reported by Object Allocation is not very autoritative, at least according to my experience. The real deal is the real memory consumption as reported by Memory Monitor, see my question on iPhone memory consumption. Your numbers seem to be measured in Simulator, such measurement is worthless. You have to measure on the device.
对象分配报告运行的整个生命周期内使用的总内存。 这意味着如果对象被分配和释放（通常是这样），您将看到总共消耗的所有内存。
更有用的是选择“已创建且仍然存在”选项，然后突出显示图表中内存增加的区域，但如果您期望的话，它永远不会减少。 然后您可以看到此时分配了多少内存以及分配的内容。 这在模拟器和设备中都有效。
Object Alloc is reporting to the total memory used over the entire lifespan of the run. That means if objects are allocated and deallocated (which they often are) you see all the memory consumed in total.
Far more useful is to select the option "created and still living", then highlight regions of the graph where memory increases but it never goes down if you expect it would. Then you can see how much memory is being allocated at that point and what is allocating it. This works in the simulator as well as the device.