Overview of memory administration Stay organized with collections Save and categorize content material primarily based in your preferences. The Android Runtime (Artwork) and Dalvik virtual machine use paging and memory-mapping (mmapping) to manage memory. Which means that any memory improvement solution an app modifies-whether by allocating new objects or touching mapped pages-remains resident in RAM and can't be paged out. The only option to launch memory from an app is to release object references that the app holds, making the memory out there to the garbage collector. That's with one exception: any recordsdata mmapped in without modification, comparable to code, will be paged out of RAM if the system desires to use that memory elsewhere. This page explains how Android manages app processes and memory allocation. For more information about find out how to handle memory more effectively in your app, see Manage Your App's Memory. A managed memory setting, just like the Artwork or Dalvik digital machine, retains track of every memory allocation. Once it determines that a bit of memory is now not being utilized by the program, it frees it again to the heap, without any intervention from the programmer.
simpli.com

The mechanism for reclaiming unused memory within a managed memory setting is known as garbage collection. Rubbish assortment has two goals: discover data objects in a program that cannot be accessed sooner or later