On Sat, Aug 27, 2011 at 1:56 PM, Jason <dummytest20@gmail.com> wrote:
Yes, because the instance is still loaded and the service holds a reference to it.
You can call System.gc(), but that is just a hint, th GC may not run.
It looks like that, check with the service provider.
1) Is it possible for instance A to be referenced even after
onDestroy() is called on it?
Yes, because the instance is still loaded and the service holds a reference to it.
2) Is there a way to immediately invoke the garbage collector to clear
out the memory space instance A is occupying?
You can call System.gc(), but that is just a hint, th GC may not run.
3) Is this a problem with the third party service? In my code i
perform bind in onCreate and unbind in onDestroy... I am stumped as to
why my destroyed instance A is still being referenced when the service
was bound to and started by B.
It looks like that, check with the service provider.
--
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
No comments:
Post a Comment