/frameworks/base/tools/preload/ |
D | Root.java | 43 final Map<Integer, Proc> processes = new HashMap<Integer, Proc>(); field in Root 55 Proc process = processes.get(record.pid); in indexClassOperation() 116 Proc proc = processes.get(record.pid); in indexProcess() 120 Proc parent = processes.get(record.ppid); in indexProcess() 122 processes.put(proc.id, proc); in indexProcess()
|
D | WritePreloadedClassFile.java | 98 for (Proc proc : root.processes.values()) { in main() 135 for (Proc proc : root.processes.values()) { in addAllClassesFrom()
|
D | PrintPsTree.java | 40 for (Proc proc : root.processes.values()) { in main()
|
D | PrintHtmlDiff.java | 43 for (Proc proc : root.processes.values()) { in main()
|
/frameworks/base/docs/html/guide/topics/processes/ |
D | process-lifecycle.jd | 35 <p>To determine which processes should be killed when low on memory, Android 59 <p>There will only ever be a few such processes in the system, and these will only 60 be killed as a last resort if memory is so low that not even these processes 72 required to keep all foreground processes running. 78 processes are not directly visible to the user, they are generally doing things 80 network data upload or download), so the system will always keep such processes 86 {@link android.app.Activity#onStop} method has been called). These processes 90 can kill such processes at any time to reclaim memory for one of the three 91 previous processes types. Usually there are many of these processes running, 99 run. As such, the system will often kill these processes in order to [all …]
|
/frameworks/webview/chromium/tools/ |
D | memreport.py | 65 processes = [] 73 processes.append(mem_usage_for_regions) 100 return processes
|
/frameworks/base/docs/html/training/articles/ |
D | memory.jd | 37 <li><a href="#MultipleProcesses">Use multiple processes</a></li> 63 <p>This document explains how Android manages app processes and memory allocation, and how you can 88 <p>In order to fit everything it needs in RAM, Android tries to share RAM pages across processes. It 95 framework code and resources to be shared across all app processes.</li> 98 between processes but also allows it to be paged out when needed. Example static data include: 103 <li>In many places, Android shares the same dynamic RAM across processes using explicitly allocated 125 which accounts for both dirty and clean pages that are shared with other processes—but only i… 159 <p>Instead of using swap space when the user switches between apps, Android keeps processes that 167 overall performance. So, as the system runs low on memory, it may kill processes in the LRU cache 169 which processes are most memory intensive. To keep your process cached as long as possible, follow [all …]
|
/frameworks/base/docs/html/guide/components/ |
D | processes-and-threads.jd | 34 different components in your application to run in separate processes, and you can create additional 37 <p>This document discusses how processes and threads work in an Android application.</p> 63 other processes that are more immediately serving the user. Application 67 <p>When deciding which processes to kill, the Android system weighs their relative importance to 71 rules used to decide which processes to terminate is discussed below. </p> 77 eventually needs to remove old processes to reclaim memory for new or more important processes. To 78 determine which processes to keep 85 types of processes in order of importance (the first process is <em>most important</em> and is 112 <p>Generally, only a few foreground processes exist at any given time. They are killed only as 114 point, the device has reached a memory paging state, so killing some foreground processes is [all …]
|
D | bound-services.jd | 132 your service is used by other applications or across separate processes.</dd> 135 <dd>If you need your interface to work across different processes, you can create 150 primitives that the operating system can understand and marshall them across processes to perform 175 <p>If your service is used only by the local application and does not need to work across processes, 204 marshalling across processes.</p> 342 <p>If you need your service to communicate with remote processes, then you can use a 600 <li>Objects are reference counted across processes. </li>
|
/frameworks/base/docs/html/tools/debugging/ |
D | annotations.jd | 81 <a href="{@docRoot}guide/components/processes-and-threads.html">thread</a>. </dd> 195 <a href="{@docRoot}guide/components/processes-and-threads.html">thread</a>. The following thread 210 <a href="{@docRoot}guide/components/processes-and-threads.html">thread</a> 212 <a href="{@docRoot}guide/components/processes-and-threads.html">thread</a>. </p> 214 <p>A common use of the <a href="{@docRoot}guide/components/processes-and-threads.html">thread</a> 218 <a href="{@docRoot}guide/components/processes-and-threads.html">thread</a>. </p>
|
D | systrace.jd | 101 you must configure the types of processes you want to trace before running a trace. 105 <li>General system processes such as graphics, audio and input processes (selected using trace 120 <li>Stop and restart the {@code adb} shell to enable tracing of these processes. 132 <li>Select the categories of processes to be traced and click <strong>OK</strong>.</li>
|
D | debugging-memory.jd | 392 …This is a measurement of your app’s RAM use that takes into account sharing pages across processes. 394 that are shared with other processes contribute to the PSS value only in proportion to the amount 395 of sharing. For example, a page that is shared between two processes will contribute half of its 400 <p>A nice characteristic of the PSS measurement is that you can add up the PSS across all processes… 401 determine the actual memory being used by all processes. This means PSS is a good measure for the 402 actual RAM weight of a process and for comparison against the RAM use of other processes and the 497 allocations (weighted by their sharing across processes, as described in the PSS definition above). 583 with other processes and the total available RAM. 586 process, which are not shared with other processes. Together (especially <code>Private Dirty</code>… 656 all app processes, they don’t matter very much to your own heap analysis.</p>
|
/frameworks/base/docs/html/sdk/installing/ |
D | studio-build.jd | 47 <p>The build process involves many tools and processes that generate intermediate files on the 52 different tools and processes that are involved in a build:</p>
|
/frameworks/base/tools/layoutlib/rename_font/ |
D | build_font.py | 93 pool = Pool(processes=None)
|
/frameworks/base/docs/html/distribute/monetize/ |
D | subscriptions.jd | 24 transactions. Google Play processes all payments for subscriptions
|
/frameworks/base/docs/html/training/multiple-threads/ |
D | index.jd | 30 <li><a href="{@docRoot}guide/components/processes-and-threads.html">Processes and Threads</a></li>
|
D | create-threadpool.jd | 20 <li><a href="{@docRoot}guide/components/processes-and-threads.html">Processes and Threads</a></li> 49 <a href="{@docRoot}guide/components/processes-and-threads.html">
|
D | define-runnable.jd | 18 <li><a href="{@docRoot}guide/components/processes-and-threads.html">Processes and Threads</a></li>
|
D | run-code.jd | 18 <li><a href="{@docRoot}guide/components/processes-and-threads.html">Processes and Threads</a></li>
|
/frameworks/base/docs/html/training/notify-user/ |
D | managing.jd | 71 // Start of a loop that processes data and then notifies the user
|
/frameworks/base/docs/html/tools/help/ |
D | index.jd | 97 <dd>Lets you analyze the execution of your application in the context of system processes, 104 <dd>Lets you analyze the execution of your application in the context of system processes,
|
D | systrace.jd | 8 displaying execution times of your applications processes and other Android system processes. The 11 device’s system processes for a given period of time.</p>
|
/frameworks/base/docs/html/preview/ |
D | behavior-changes.jd | 53 permissions, while streamlining the installation and auto-update processes for app developers. 255 processes are favored. Changes to the service behavior include:</p> 258 awarded based on the “priority” of the client application process. Application processes with 268 <li>On devices with appropriate camera hardware, separate application processes are able to 279 processes that use the camera subsystem when the user has switched to a different account.
|
/frameworks/base/docs/html/tools/performance/batterystats-battery-historian/ |
D | index.jd | 34 <li>Showing you where and how processes are drawing current from the battery.</li>
|
/frameworks/base/docs/html/training/basics/network-ops/ |
D | xml.jd | 122 <code>readFeed()</code> method, which extracts and processes the data the app is 434 parameter. The method <code>loadXmlFromNetwork()</code> fetches and processes 527 // This section processes the entries list to combine each entry with HTML markup.
|