| /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 | 136 your service is used by other applications or across separate processes.</dd>
139 <dd>If you need your interface to work across different processes, you can create
154 primitives that the operating system can understand and marshall them across processes to perform
179 <p>If your service is used only by the local application and does not need to work across processes,
208 marshalling across processes.</p>
349 <p>If you need your service to communicate with remote processes, then you can use a
608 <li>Objects are reference counted across processes. </li>
|
| D | aidl.jd | 336 marshalled across processes.</p>
418 data from other processes. In this case, the {@code Rect} reads four numbers from the {@link
453 <li>Objects are reference counted across processes. </li>
|
| /frameworks/base/docs/html/preview/features/ |
| D | background-optimization.jd | 50 Background processes can be memory- and battery-intensive. For example, an
51 implicit broadcast may start many background processes that have registered
52 to listen for it, even if those processes may not do much work. This can have
106 register to receive them in their manifest, and processes that depend on this
366 background processes entirely.
372 you can use to test app behavior with those background processes disabled:
|
| D | direct-boot.jd | 121 <li>If your app has foreground processes that need immediate notification,
123 <li>If your app only uses background processes that can act on a delayed
|
| /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/about/versions/marshmallow/ |
| D | android-6.0-changes.jd | 56 permissions, while streamlining the installation and auto-update processes for app developers.
248 processes are favored. Changes to the service behavior include:</p>
251 awarded based on the “priority” of the client application process. Application processes with
261 <li>On devices with appropriate camera hardware, separate application processes are able to
272 processes that use the camera subsystem when the user has switched to a different account.
|
| /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.
|
| /frameworks/base/docs/html/training/run-background-service/ |
| D | report-status.jd | 189 {@link android.app.Activity} receives and processes {@link android.content.Intent} objects even
|
| /frameworks/base/docs/html/guide/topics/manifest/ |
| D | provider-element.jd | 220 processes, and "{@code false}" if not. The default value is "{@code false}".
271 application across multiple processes.
|
| /frameworks/base/docs/html/preview/ |
| D | behavior-changes.jd | 317 all its background processes. This means that if a user switches away from
321 processes, the system notifies those processes of the configuration change as
326 <li>If an app targets Android N, all of its processes
|
| /frameworks/base/docs/html-intl/intl/zh-cn/guide/components/ |
| D | services.jd | 115 …ava.lang.Thread} 类。如需了解有关线程的详细信息，请参阅<a href="{@docRoot}guide/components/processes-and-threads.html…
174 …稍后会对此加以讨论）。如需了解有关系统会在何时销毁服务的详细信息，请参阅<a href="{@docRoot}guide/components/processes-and-threads.html…
|