3 ms·

The Linux kernel has used the SLUB memory manager (and Android is just Linux) since major kernel release 2.6.23 so I'm very confused by your post? Remember, me

The Linux kernel has used the SLUB memory manager (and Android is just Linux) since major kernel release 2.6.23 so I'm very confused by your post? Remember, memory is like a keg of beer, if everyone drinks it all, it's gone regardless of how you "distribute" it to people into smaller sized Solo cups or whatever. I can think of a few things that could help but not solve the problem, but the crux of the problem is that it's still a finite resource: https://developer.android.com/topic/performance/memory-overview.html https://developer.android.com/topic/performance/memory-overv... Working against that, you also have Gates' Law.

morganvachon 10y ago
Well, Android isn't "just Linux", if that were the case it wouldn't be able to run any Android apps. Anyway, it's my understanding that Android uses custom heap size limits to help keep things running smoothly. This combined with efficient garbage collection makes for a generally smooth user experience on a constrained device like a phone or tablet. Android will cache, and later kill, processes that aren't being used, to free up memory for active processes. Memory may be a finite resource, but not in the way you described; it's not permanently used up and can always be freed for foreground tasks.