You could also be more proactive with releasing unneeded objects. Rather than doing it in finalize (if that is how you do it), do object cleanup in onPause.
18.05.2010 23:12 пользователь "ls02" <[email protected]> написал: Yes, this is really what I need. Though I see that periodically my singleTask activity contsractor and onCreate are called which means that activity instance is probably periodically destroyed though the activity's finalize is not called. But I tested my sample app and it runs without running out of memory. It also seems that there is no need to handle onNewIntent, activity "refresh" can be done from onResume. On May 18, 2:14 pm, Streets Of Boston <[email protected]> wrote: > What about setting your ac... > > -- > > You received this message because you are subscribed to the Google > > Groups "Android De... > For more options, visit this group athttp:// groups.google.com/group/android-developers?hl=en -- ... For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- 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] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
