By default, android use low memory killer to try to get out of phone low memory situation.
But sometimes, the killer killed process that should not killed. That happened as the killer cannot understand what is "should not killed" from application layer. For example: 1) a persistent process hosting a service (like mp3 background playing, or a phone local search engine with DB hooks) has been killed, and the process itself will startup again. that sometimes drop into the process kill-restart-died cycle. User cannot feel that directly from UI, but that waste CPU and electric. or user will curious about why the mp3 playing in background always lost. 2) a process hosting a provider has been killed, but unfortunately a application is just calling the provider for data. user will see the application exception happened. Do you ever face a similar issue? And besides low memory killer, do you have any practice way to handle phone low memory situation more efficiently? Thanks a lot! -- 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
