On Jun 1, 1:33 pm, Matt <[email protected]> wrote:
> 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)

Whole processes are killed, usually without any warning to the process
involved.

> 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)

We don't have a "JVM" on Android.  "DVM" is more appropriate.

Dalvik will give back pages.  Every VM has a HeapWorker thread that
wakes up occasionally to run finalizers and give back 4KB pages.  It
doesn't do it right when the memory is freed because there's a fair
chance that it'll get used again immediately, and we don't want to
thrash the system with unnecessary system calls.

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to