Searched refs:killed (Results 1 – 22 of 22) sorted by relevance
35 <p>To determine which processes should be killed when low on memory, Android60 be killed as a last resort if memory is so low that not even these processes71 process is considered extremely important and will not be killed unless doing so is93 by the user is the last to be killed when running low on memory.
126 boolean killed = false; in loop()127 while (!killed) { in loop()163 killed = true; in loop()
114 boolean killed; // True once we know the process has been killed field in ProcessRecord336 if (killed || killedByAm || waitingToKill != null) { in dump()337 pw.print(prefix); pw.print("killed="); pw.print(killed); in dump()548 killed = true; in kill()
2774 if (!app.killed) { in removeLruProcessLocked()3373 app.killed = false; in startProcessLocked()4654 if (!app.killed) { in appDiedLocked()4659 app.killed = true; in appDiedLocked()11184 boolean killed = false; in killPids()11221 killed = true; in killPids()11225 return killed; in killPids()11257 boolean killed = false; in killProcessesBelowAdj()11268 killed = true; in killProcessesBelowAdj()11272 return killed; in killProcessesBelowAdj()
80 from the device and all applications running on the external storage are immediately killed.</p>123 installed on the external storage and currently running is killed. The system effectively becomes133 <dd>Your running {@link android.app.Service} will be killed and will not be restarted when188 process is killed, there should be no visible effect when the storage becomes available again and
72 strings. This data will persist across user sessions (even if your application is killed).</p>
174 can be killed is available in the <a href="{@docRoot}guide/components/processes-and-threads.html"268 <p>Your app is still running, but the system has already killed most of the processes in the280 Although your app process is not at a high risk of being killed, the system may already be killing287 system becomes further constrained for memory, there's a chance your process will be killed.</p>291 <p>The system is running low on memory and your process is one of the first to be killed if the305 consuming more memory and will thus provide the system more memory gain if killed.708 needed elsewhere. These services are still quite expensive because they can be killed only712 prevent it from being killed as much as possible. Killing this process is much more damaging to the717 and so should be killed more aggressively when RAM is needed elsewhere.</li>723 eventually be killed. If the service should continue running (as defined by the {@link
202 is paused at the very least, and may be killed altogether if the205 state it was in when it was killed.</p>223 Activity is being stopped and <strong>may be killed before it is
40 be killed. In order to check this box, you must have selected a debug application as described
26 Currently, the application is killed when the user stops tracing from the frontend GUI. We need
64 components running in the process that's killed are consequently destroyed. A process is started86 <em>killed last</em>):</p>112 <p>Generally, only a few foreground processes exist at any given time. They are killed only as132 <p>A visible process is considered extremely important and will not be killed unless doing so152 recently seen by the user is the last to be killed. If an activity implements its lifecycle methods
363 the window manager), but can be killed by the system in extremely low memory situations.</dd>370 can be killed by the system when memory is needed elsewhere.</dd>375 process. When the activity is opened again (after being finished or killed), it must be created all580 last method that's guaranteed to be called before the process <em>can</em> be killed—if590 activity from being killed from the moment they are called. Thus, an activity is killable596 definition in table 1 might still be killed by the system—but that would happen only in597 extreme circumstances when there is no other recourse. When an activity might be killed is
169 focus, then it's less likely to be killed, and if the service is declared to <a170 href="#Foreground">run in the foreground</a> (discussed later), then it will almost never be killed.448 // If we get killed, after returning from here, restart728 int mStartMode; // indicates how to behave if the service is killed
667 visible to the user and will be killed if the activity is killed.</dd>671 android.os.Bundle}, in case the activity's process is killed and you need to restore the
529 lost, such as when the service has crashed or has been killed. This is <em>not</em> called when the
73 your application being killed.</p>77 killed. Unless, of course, you save the work in progress first. The "Android
74 your application being killed.</p>78 killed. Unless, of course, you save the work in progress first. The "Android
178 task like a phone call, and while in the background it might be killed and the memory cache
313 …e life-cycle, in particular low memory situations where a Service may be killed while it is runnin…
900 <dd>Whether or not the activity can be killed and successfully restarted
565 cases in which the service gets killed.</li>
META-INF/ META-INF/MANIFEST.MF android/ android/databinding/ android/ ...