HomeSort by relevance Sort by last modified time
    Searched full:killed (Results 1 - 25 of 422) sorted by null

1 2 3 4 5 6 7 8 91011>>

  /external/chromium/chrome/browser/ui/gtk/
sad_tab_gtk.h 20 KILLED // The tab was killed. Display the killed tab page.
  /external/chromium/chrome/browser/ui/views/
sad_tab_view.h 30 KILLED // The tab was killed. Display the killed tab page.
  /external/llvm/test/Transforms/GlobalDCE/
2002-08-17-FunctionDGE.ll 9 ;; Should die when function %foo is killed
2002-09-12-Redeletion.ll 3 ;; Should die when function %foo is killed
  /external/webkit/Source/WebCore/storage/
LocalStorageThread.cpp 77 ASSERT(!m_queue.killed() && m_threadID);
84 ASSERT(!m_queue.killed() && m_threadID);
92 ASSERT(m_queue.killed());
  /development/samples/HeavyWeight/res/values/
strings.xml 19 <string name="content_text">A heavy-weight application will not be killed until explicitly stopped.</string>
  /packages/apps/DeskClock/src/com/android/deskclock/
AlarmAlertFullScreen.java 101 // Register to get the alarm killed/snooze/dismiss intent.
203 private void dismiss(boolean killed) {
204 Log.i(killed ? "Alarm killed" : "Alarm dismissed by user");
205 // The service told us that the alarm has been killed, do not modify
207 if (!killed) {
245 // No longer care about the alarm being killed.
  /development/tools/axl/
chewie.py 71 killed = [[], []]
120 killed[0].append(record[9])
121 killed[1].append(x[0])
155 pylab.plot(killed[1], killed[0], 'rx')
  /packages/apps/Exchange/src/com/android/exchange/service/
ExchangeBroadcastProcessorService.java 34 * <li>So that it's less likely for the process to get killed.
46 // Intent should be redelivered if the process gets killed before completing the job.
  /development/samples/HeavyWeight/src/com/example/android/heavyweight/
HeavyWeight.java 26 * Basic "heavy-weight" application, which will not be killed by Android
  /external/chromium/chrome/browser/
oom_priority_manager.h 19 // algorithm embedded here for priority in being killed upon OOM
oom_priority_manager.cc 60 // Returns true if |first| is considered less desirable to be killed
144 // killed is first, most desirable is last.
155 // values are more likely to be killed by the OOM killer. We also
  /external/llvm/utils/lit/lit/ExampleTests/Clang/
lit.cfg 10 # For now we require '&&' between commands, until they get globally killed and
  /external/llvm/include/llvm/CodeGen/
LiveVariables.h 15 // killed).
61 /// In the common case where a value is defined and killed in the same block,
68 /// the block (unless the value is defined and killed in the same block) and
115 /// MBB, or it is killed in MBB. If Reg is only used by PHI instructions in
206 /// specified register is killed after being used by the specified
217 /// variable was marked as killed by the specified instruction,
237 /// removeVirtualRegistersKilled - Remove all killed info for the specified
295 /// PHI nodes. This means that Reg is either killed by a successor block or
  /external/chromium/chrome/browser/renderer_host/
web_cache_manager_browsertest.cc 37 ResultCodes::KILLED, true);
  /external/srtp/test/
rtpw_test.sh 18 # they are killed, those processes will linger. Re-running the script
  /frameworks/base/core/java/android/content/
ServiceConnection.java 44 * happens when the process hosting the service has crashed or been killed.
  /frameworks/base/docs/html/guide/topics/processes/
process-lifecycle.jd 35 <p>To determine which processes should be killed when low on memory, Android
60 be killed as a last resort if memory is so low that not even these processes
71 process is considered extremely important and will not be killed unless doing so is
93 by the user is the last to be killed when running low on memory.
  /frameworks/base/core/java/android/app/
Service.java 189 * being killed.
194 * the service should not be killed except in extreme low memory conditions.
203 * the service to be killed under extreme memory pressure from the current
208 * be killed by the system if it is under heavy memory pressure. If this
214 * is killed while processing it.
306 * the service if it is killed. May be {@link #START_STICKY},
315 * {@link #onStartCommand} will be called again after being killed.
321 * process is killed while it is started (after returning from
338 * process is killed while it is started (after returning from
354 * and spawns a thread to do its networking. If its process is killed
    [all...]
  /external/chromium/chrome/browser/ui/views/tabs/
base_tab.cc 190 // When --reload-killed-tabs is specified, then the idea is that
191 // when tab is killed, the tab has no visual indication that it
193 // the user seeing the killed tab page.
198 // will constantly get killed, or if it's the only tab. So this
200 // killed tabs when the tab is currently selected.
203 // If we're reloading killed tabs, we don't want to display
204 // the crashed animation at all if the process was killed and
  /frameworks/base/docs/html/resources/articles/
multitasking-android-way.jd 48 <p>If a user later returns to an application that's been killed, Android needs a way to re-launch it in the same state as it was last seen, to preserve the "all applications are running all of the time" experience. This is done by keeping track of the parts of the application the user is aware of (the Activities), and re-starting them with information about the last state they were seen in. This last state is generated each time the user leaves that part of the application, not when it is killed, so that the kernel can later freely kill it without depending on the application to respond correctly at that point.</p>
49 <p>In some ways, Android's process management can be seen as a form of swap space: application processes represent a certain amount of in-use memory; when memory is low, some processes can be killed (swapped out); when those processes are needed again, they can be re-started from their last saved state (swapped in).</p>
51 <p>So far, we have a way for applications to implicitly do work in the background, as long as the process doesn't get killed by Android as part of its regular memory management. This is fine for things like loading web pages in the background, but what about features with harder requirements? Background music playback, data synchronization, location tracking, alarm clocks, etc.</p>
56 <p>When handling a broadcast, the application is given a fixed set of time (currently 10 seconds) in which to do its work. If it doesn't complete in that time, the application is considered to be misbehaving, and its process immediately tossed into the background state to be killed for memory if needed.</p>
62 <p>If there is too little RAM, processes hosting services will be immediately killed like background processes are. However, if appropriate, Android will remember that these services wish to remain running, and restart their process at a later time when more RAM is available. For example, if the user goes to a web page that requires large amounts of RAM, Android may kill background service processes like sync until the browser's memory needs go down.</p>
  /external/mesa3d/src/glsl/
opt_copy_propagation.cpp 98 * List of kill_entry: The variables whose values were killed in this
258 * cloned minus the killed entries after the first run through.
298 /* Add the LHS variable to the list of killed variables in this block.
  /bionic/libc/include/sys/
_sigdefs.h 46 __BIONIC_SIGDEF(KILL,9,"Killed")
  /development/ndk/platforms/android-3/include/sys/
_sigdefs.h 41 __BIONIC_SIGDEF(SIGKILL,9,"Killed")
  /development/ndk/platforms/android-9/include/sys/
_sigdefs.h 46 __BIONIC_SIGDEF(KILL,9,"Killed")

Completed in 5111 milliseconds

1 2 3 4 5 6 7 8 91011>>