Searched refs:killed (Results 1 – 7 of 7) sorted by relevance
229 * The reason code that why app process is killed.253 * Application process was killed by the system low memory killer, meaning the system was269 * Application process was killed due to being unresponsive (ANR).274 * Application process was killed because it took too long to attach to the system280 * Application process was killed because of initialization failure,287 * Application process was killed by the activity manager due to excessive resource usage.292 * Application process was killed because of the user request, for example,299 * Application process was killed, because the user they are running as on devices305 * Application process was killed because its dependency was going away, for example,306 * a stable content provider connection's client will be killed if the provider is killed.[all …]
153 verbose_print "[LOGCAT] $logcat_pid should be killed"
126 boolean killed = false; in loop()127 while (!killed) { in loop()163 killed = true; in loop()
788 void setKilled(boolean killed) { in setKilled() argument789 mKilled = killed; in setKilled()
7132 boolean killed = false; in killPids()7168 killed = true; in killPids()7183 return killed; in killPids()7242 boolean killed = false; in killProcessesBelowAdj()7256 killed = true; in killProcessesBelowAdj()7262 return killed; in killProcessesBelowAdj()
29 … timeout time for a window to prevent the ANR dialog from appearing or the app from getting killed.
970 * Logs when a cached process is killed, along with its pss.14881 * Logs the current state of an application before it is killed.14890 // Name of the package that was killed.14893 // State of the application when it was killed.14921 // Stats of the processes owned by the application when the application was killed.14922 // The process stack traces are not collected when the application was killed due to IO_OVERUSE.