On Thu, Mar 26, 2009 at 10:19 AM, Stoyan Damov <[email protected]>wrote:
> So, ok, I *admit* other apps can't cause DIRECTLY a GC in my app, but > it doesn't matter to me because other apps can cause the system to > lack memory and perform GC and it would ask my app's process to do GC, > which is how I understand JBQ's explanation of "remote GC". > > So back to my point. I don't care what causes GC in *my* process. If > it's not me I DON'T want my process to be bothered at all. There is no way at all for other processes to cause your process to GC. What other processes -can- do is run some work -- any kind of work -- on a thread running at the same or higher priority as yours, causing you to have to share the CPU with them. GCs are irrelevant to the problem here. (But they -are- relevant to writing your own code so that you don't cause GCs to happen in your own process.) Currently our approach for scheduling is that apps doing background work on a thread should lower that thread's priority -- the standard applications on Android do this. This has holes however, and allows people to mistakenly do background work at a higher priority, so we should more strongly enforce the scheduling of processes that are not running the foreground UI. -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
