Re: [android-developers] Correct way to implement Activity onDestroy()?

Basically, as long as you aren't hanging static Activity references
you should be fine. The main activity will be thrown away upon its
destruction, at which point the Activity will be thrown away: along
with its contents. Of course, if you're holding onto Views elsewhere
that's bad (i.e., don't hold static refs).

kris

On Mon, Jan 14, 2013 at 1:42 AM, Greenhand <cooperateonline@gmail.com> wrote:
> I read
> http://android-developers.blogspot.tw/2009/01/avoiding-memory-leaks.html
> about avoiding memory leaks.
> I would like to know whether I should null out all member variables, such as
> TextView and Button in onDestroy()? Or, unregistering listener, unbinding
> service and etc.in onDestroy() are enough to prevent 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 android-developers@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscribe@googlegroups.com
> 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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en