1. In the event that the Android system is running low on memory, Android starts shutting down activities and/or processes. Can Android shut down individual components, as opposed to the whole process? In other words, can Android close down an activity but leave the service running? (I believe the answer is 98% yes, but there were some ambiguities on the Android dev framework page)
2. Presuming the answer to 1 is yes, imagine a scenario where an Activity is shut down, but a Service is still running. If the Android OS shuts down that Activity, do all of the Java Threads that were created by that Activity get terminated? If so, I’d like to know more about how that works, because as I understood it, all Services and Activities run on the same thread, so how would one child thread get marked to an activity but not the service. (We have a thread that is going to work with both Services and Activities) 3. Do the JVMs built in with Android (Davik JVMs) have the ability to release memory to the system that it longer uses? Win32 Sun Java JVMs do not do this (once they ask for more memory, they will never release it back to the system; you will see on Win32 a java.exe grow in memory used, but never shrink) The reason we ask, is that we want to know this: If one calls finish() on an Activity, and that Activity is closed, but the process that holds that Activity is still running, does the process itself release the memory back to the system? (because on Win32, you will never see java.exe release memory after a GC; it is only tagged internally to the JVM as free, not to the OS) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
