Strange Memory Issue

[jms123]

I have an application that runs smoothly for a period of time. Occasionally, the didRecieveMemoryWarning fires, I free up cached data and continue on. However, when I close out of the app then relaunch, the app the didReceiveMemoryWarning event fires often. It seems as if my app memory is not fully being released, even when the application is completely closed.

If I reboot the phone the application performs much better. Is there a way to ensure memory is cleared completely when the app is closed? I used Instruments to check for leaks and there aren't any that I can see. Even if there were leaks wouldn't the memory be flushed when I quit the app? Any thoughts? Thanks.

[ecume]

the answer typically given for this is "memory fragmentation" - although I am also not sure exactly what this means or how to reduce it. It does seem better on 2.2 (for me). I had terrible problems with this under 2.0...my app would basically only run properly directly after a restart. Some games recommend restarting before playing the game, presumably for the same reason.

[mpramodjain]

[quote=jms123;33137]I have an application that runs smoothly for a period of time. Occasionally, the didRecieveMemoryWarning fires, I free up cached data and continue on. However, when I close out of the app then relaunch, the app the didReceiveMemoryWarning event fires often. It seems as if my app memory is not fully being released, even when the application is completely closed.

Hi,

Can u help me with a snippets of code on how to free up the cached data programmatically.

Also if u find the solution for the your problem , please share, I am also getting much problems with application running after a few minutes.

Thank u.

[moo_gamer]

Hey,

Would you please tell me, how do you release cache?

Whats the code for release cache?