Hi, Anyone encounter such problem? Use eclipse to profile your application, and monitor your memory heap size usage.
Your application works like this, Activity A start subactivity B, B call setResult(), finish() and return to A, then do previous action again and again. I call System.gc() just before B call fnish(), the eclipse heap monitor will refresh its value. The result is, even the subactivity B was killed totally (from logcat log), the memory usage always keep increasing. GC seems not work. Okay... I suppose it will not do real gc before the memory usage haven't reach a certain value, but the final result of this kind of actions (close and start subactivity) is the memory leak. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
