I am developing an RSS reader type iPhone application and this is going to be complete, though I will be 4.3 tomorrow with iOS I'm upgrading to Xcode 4. And I have attended some serious memory issues. My app now receives memory warnings now, I'm dealing with rediscovery memory warning, and release all my cached images, but it does not provide a good user experience is. I am also using instruments in an attempt to diagnose this problem, but it is raising more questions.
one ?? ¢ Does SDK 4.3 use more memory? I did not receive memory warnings before upgrading, not sure whether it is relevant or not, but I'm mostly testing with my iPhone test on my iPhone 4.2 (4.3 is not supported on 3G) .
one ?? ¢ Why does the allocation tool tool do not match the actual memory column in the live byte column activity monitor tool? The Activity Monitor tool always reports more memory usage.
â? ¢ According to the leak my app does not leak into the simulator or the memory on the actual iPhone, but when I look at the allocation, it seems that as I think the transition between thoughts and then pop thoughts, the live bytes column is in my previous values Does not come back in, which is equivalent to leak memory? (Yes released after the pop-up)
â? ¢ My app often reports memory warning at startup, but when I design the application with leaks, does the leak cause additional memory overhead?
one ?? ¢ Perhaps this is a difficult question, but what is the proper memory footprint for an iPhone app? When I am leaking, my app can almost be run in few minutes due to low memory, but with the allocation report in leak tool I am using 2 MB when the app is over.
one ?? ¢ Why does the activity Monitor tool do a column for virtual memory? Everything I read says that the iPhone does not use virtual memory? 4.3 SDK probably uses more memory, but if this is a question that you are asking for, then
You are probably on the wrong track, because as a developer, your app should not be the reason for being static.
I will not be worried about this, the discrepancies between the report of the Allocation Report and the Activity Monitor report, it is not uncommon for the memory footprint to grow because ideas are pushed and pops up, and shrinking does not happen. Another answer tells this event in a better description.
The proper memory footprint for iOS app is the smallest amount of your app to work.
IOS actually virtual memory From Apple's Memory Usage Performance Guidelines:
Both Mac OS X and iOS include a fully integrated virtual memory system that you can not stop; It always happens at both the systems providing 4 gigabytes of address addresses for the 32-bit process.
...
Although Mac OS X supports a backing store, iOS does not. In the iPhone applications, data that is already read on disk (such as code pages) is simply removed from memory and reloaded from disk as needed. The writeable data is never removed from memory by the operating system. Instead, if the amount of free memory falls below a certain threshold, then the system is running the system to free up the space for new data to make it voluntary Says. Failure to free up enough memory are terminated.
I can read you through the entire document, especially you can also use the build-end-knowledge facility, which can be used to identify many types of bugs, including memory leaks Uses the built-in cleng
Comments
Post a Comment