Salvador, I think you may be a bit confused as to how process loading/killing works.
If we kill the homescreen app, for example, when you return to the homescreen, we'll re-load it. It's not a great experience for users, but it is not correct that the phone is useless if we kill the homescreen app. The keyboard app runs in the system process for B2G v1 so is not susceptible to being killed currently. I agree that we shouldn't kill the dialer app while you're talking, even if the dialer app is in the background. We have a number of bugs about tuning these heuristics, but we are in the early stages of this work. We intend to keep these heuristics simple; for example, it is not a goal to allow users to configure exactly which apps are preferentially kept alive. Instead, we will focus on keeping "active" apps (such as the currently visible app; the hypothetical OOP keyboard, if it's currently shown; and the app handling an active call) from being killed. See bug 768832 for some of the work that we're doing here. Thanks. On Tue, Oct 30, 2012 at 2:02 PM, Salvador de la Puente González <[email protected]> wrote: > Hello everybody > > As I said in Gaia meeting today, I'm a little bit concerned about B2G > memory optimizer and what kind of applications it can kill automatically. > > I don't know what is the component name but I know its function is to > close applications automatically when the device is running out of > memory. But I think we should prioritize applications distinguishing > between those that are essential for the proper operation of the device. > Note, AFAIK, as soon as an application is OOP, it is eligible to be > killed when no more memory is available. Despite usage criteria, > applications such as homescreen, dialer (think about emergency calls), > keyboard (consider its big dictionary) or first run experience should be > auto-closed only if there is **no other way** to free memory. > > So I propose **to indicate the priority in the application manifest**. > Of course, a non certified application should not be privileged... Or > may this decision should be taken by the user via Settings? > > I propose four levels of prioritization: > > NOTE: > - Names don't say anything about prioritization but about the > application's importance instead. > - Priorities between brackets were available only for certified > applications. > > * [critical]: without these applications, the device is useless -> > prevent optimizer to close the application at all. I.e: system, > homescreen, first running experience and dialer > * [desirable]: applications that complete the device experience but > are not essential for the device to be useful -> schedule the > application to be closed in last term. I.e: keyboard, cost control... > * favourite: applications that the user would like to kept alive -> > these applications should be kept open but if there are no default (see > below) applications, then these will be closed. I.e: sms, facebook... > * default: normal behaviour -> these applications will be closed in > first term. I.e: calculator, maps... > > What do you think about this? > > Thank you. > > ________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar > nuestra política de envío y recepción de correo electrónico en el enlace > situado más abajo. > This message is intended exclusively for its addressee. We only send and > receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
