adb shell dumpsys meminfo <packageName> [-d] 查看app(进程)的内存占用（未完待续）

1、官方有篇文章，详细的写了，可以通过哪些工具查看内存占用的情况
https://developer.android.com/studio/profile/investigate-ram.html
2、我们只说其中的 adb shell dumpsys meminfo，下面是官方原文  个人记忆：dump  + sys    memory + info， 即dumpsys meminfo

Viewing Overall Memory Allocations
For further analysis, you may want to observe how your app's memory is divided between different types of RAM allocation with the following adb command:

adb shell dumpsys meminfo <package_name|pid> [-d]
The -d flag prints more info related to Dalvik and ART memory usage.

The output lists all of your app's current allocations, measured in kilobytes.

When inspecting this information, you should be familiar with the following types of allocation:

Private (Clean and Dirty) RAM
This is memory that is being used by only your process. This is the bulk of the RAM that the system can reclaim when your app’s process is destroyed. Generally, the most important portion of this is “private dirty” RAM, which is the most expensive because it is used by only your process and its contents exist only in RAM so can’t be paged to storage (because Android does not use swap). All Dalvik and native heap allocations you make will be private dirty RAM; Dalvik and native allocations you share with the Zygote process are shared dirty RAM.
Proportional Set Size (PSS)
This is a measurement of your app’s RAM use that takes into account sharing pages across processes. Any RAM pages that are unique to your process directly contribute to its PSS value, while pages that are shared with other processes contribute to the PSS value only in proportion to the amount of sharing. For example, a page that is shared between two processes will contribute half of its size to the PSS of each process.
A nice characteristic of the PSS measurement is that you can add up the PSS across all processes to determine the actual memory being used by all processes. This means PSS is a good measure for the actual RAM weight of a process and for comparison against the RAM use of other processes and the total available RAM.

For example, below is the the output for Map’s process on a Nexus 5 device. There is a lot of information here, but key points for discussion are listed below.

adb shell dumpsys meminfo com.google.android.apps.maps -d
Note: The information you see may vary slightly from what is shown here, as some details of the output differ across platform versions.

** MEMINFO in pid 18227 [com.google.android.apps.maps] **
Pss  Private  Private  Swapped     Heap     Heap     Heap
Total    Dirty    Clean    Dirty     Size    Alloc     Free
------   ------   ------   ------   ------   ------   ------
Native Heap    10468    10408        0        0    20480    14462     6017
Dalvik Heap    34340    33816        0        0    62436    53883     8553
Dalvik Other      972      972        0        0
Stack     1144     1144        0        0
Gfx dev    35300    35300        0        0
Other dev        5        0        4        0
.so mmap     1943      504      188        0
.apk mmap      598        0      136        0
.ttf mmap      134        0       68        0
.dex mmap     3908        0     3904        0
.oat mmap     1344        0       56        0
.art mmap     2037     1784       28        0
Other mmap       30        4        0        0
EGL mtrack    73072    73072        0        0
GL mtrack    51044    51044        0        0
Unknown      185      184        0        0
TOTAL   216524   208232     4384        0    82916    68345    14570

Dalvik Details
.Heap     6568     6568        0        0
.LOS    24771    24404        0        0
.GC      500      500        0        0
.JITCache      428      428        0        0
.Zygote     1093      936        0        0
.NonMoving     1908     1908        0        0
.IndirectRef       44       44        0        0

Objects
Views:       90         ViewRootImpl:        1
AppContexts:        4           Activities:        1
Assets:        2        AssetManagers:        2
Local Binders:       21        Proxy Binders:       28
Parcel memory:       18         Parcel count:       74
Death Recipients:        2      OpenSSL Sockets:        2
Here is an older dumpsys on Dalvik of the gmail app:

** MEMINFO in pid 9953 [com.google.android.gm] **
Pss     Pss  Shared Private  Shared Private    Heap    Heap    Heap
Total   Clean   Dirty   Dirty   Clean   Clean    Size   Alloc    Free
------  ------  ------  ------  ------  ------  ------  ------  ------
Native Heap      0       0       0       0       0       0    7800    7637(6)  126
Dalvik Heap   5110(3)    0    4136    4988(3)    0       0    9168    8958(6)  210
Dalvik Other   2850       0    2684    2772       0       0
Stack     36       0       8      36       0       0
Cursor    136       0       0     136       0       0
Ashmem     12       0      28       0       0       0
Other dev    380       0      24     376       0       4
.so mmap   5443(5) 1996    2584    2664(5) 5788    1996(5)
.apk mmap    235      32       0       0    1252      32
.ttf mmap     36      12       0       0      88      12
.dex mmap   3019(5) 2148       0       0    8936    2148(5)
Other mmap    107       0       8       8     324      68
Unknown   6994(4)    0     252    6992(4)    0       0
TOTAL  24358(1) 4188    9724   17972(2)16388    4260(2)16968   16595     336

Objects
Views:    426         ViewRootImpl:        3(8)
AppContexts:      6(7)        Activities:        2(7)
Assets:      2        AssetManagers:        2
Local Binders:     64        Proxy Binders:       34
Death Recipients:      0
OpenSSL Sockets:      1

SQL
MEMORY_USED:   1739
PAGECACHE_OVERFLOW:   1164          MALLOC_SIZE:       62
Generally, you should be concerned with only the Pss Total and Private Dirty columns. In some cases, the Private Clean and Heap Alloc columns also offer interesting data. Here is some more information about the different memory allocations (the rows) you should observe:

Dalvik Heap
The RAM used by Dalvik allocations in your app. The Pss Total includes all Zygote allocations (weighted by their sharing across processes, as described in the PSS definition above). The Private Dirty number is the actual RAM committed to only your app’s heap, composed of your own allocations and any Zygote allocation pages that have been modified since forking your app’s process from Zygote.
Note: On newer platform versions that have the Dalvik Other section, the Pss Total and Private Dirty numbers for Dalvik Heap do not include Dalvik overhead such as the just-in-time compilation (JIT) and GC bookkeeping, whereas older versions list it all combined under Dalvik.

The Heap Alloc is the amount of memory that the Dalvik and native heap allocators keep track of for your app. This value is larger than Pss Total and Private Dirty because your process was forked from Zygote and it includes allocations that your process shares with all the others.

.so mmap and .dex mmap
The RAM being used for mapped .so (native) and .dex (Dalvik or ART) code. The Pss Total number includes platform code shared across apps; the Private Clean is your app’s own code. Generally, the actual mapped size will be much larger—the RAM here is only what currently needs to be in RAM for code that has been executed by the app. However, the .so mmap has a large private dirty, which is due to fix-ups to the native code when it was loaded into its final address.
.oat mmap
This is the amount of RAM used by the code image which is based off of the preloaded classes which are commonly used by multiple apps. This image is shared across all apps and is unaffected by particular apps.
.art mmap
This is the amount of RAM used by the heap image which is based off of the preloaded classes which are commonly used by multiple apps. This image is shared across all apps and is unaffected by particular apps. Even though the ART image contains Object instances, it does not count towards your heap size.
.Heap (only with -d flag)
This is the amount of heap memory for your app. This excludes objects in the image and large object spaces, but includes the zygote space and non-moving space.
.LOS (only with -d flag)
This is the amount of RAM used by the ART large object space. This includes zygote large objects. Large objects are all primitive array allocations larger than 12KB.
.GC (only with -d flag)
This is the amount of internal GC accounting overhead for your app. There is not really any way to reduce this overhead.
.JITCache (only with -d flag)
This is the amount of memory used by the JIT data and code caches. Typically, this is zero since all of the apps will be compiled at installed time.
.Zygote (only with -d flag)
This is the amount of memory used by the zygote space. The zygote space is created during device startup and is never allocated into.
.NonMoving (only with -d flag)
This is the amount of RAM used by the ART non-moving space. The non-moving space contains special non-movable objects such as fields and methods. You can reduce this section by using fewer fields and methods in your app.
.IndirectRef (only with -d flag)
This is the amount of RAM used by the ART indirect reference tables. Usually this amount is small, but if it is too high, it may be possible to reduce it by reducing the number of local and global JNI references used.
Unknown
Any RAM pages that the system could not classify into one of the other more specific items. Currently, this contains mostly native allocations, which cannot be identified by the tool when collecting this data due to Address Space Layout Randomization (ASLR). As with the Dalvik heap, the Pss Total for Unknown takes into account sharing with Zygote, and Private Dirty is unknown RAM dedicated to only your app.
TOTAL
The total Proportional Set Size (PSS) RAM used by your process. This is the sum of all PSS fields above it. It indicates the overall memory weight of your process, which can be directly compared with other processes and the total available RAM.
The Private Dirty and Private Clean are the total allocations within your process, which are not shared with other processes. Together (especially Private Dirty), this is the amount of RAM that will be released back to the system when your process is destroyed. Dirty RAM is pages that have been modified and so must stay committed to RAM (because there is no swap); clean RAM is pages that have been mapped from a persistent file (such as code being executed) and so can be paged out if not used for a while.

ViewRootImpl
The number of root views that are active in your process. Each root view is associated with a window, so this can help you identify memory leaks involving dialogs or other windows.
AppContexts and Activities
The number of app Context and Activity objects that currently live in your process. This can be useful to quickly identify leaked Activity objects that can’t be garbage collected due to static references on them, which is common. These objects often have a lot of other allocations associated with them and so are a good way to track large memory leaks.
Note: A View or Drawable object also holds a reference to the Activity that it's from, so holding a View or Drawable object can also lead to your app leaking an Activity.

3、使用方法，官方非常清楚，看下例子，其中 -d 是可选的参数。 语法： adb shell dumpsys meminfo <packageName> [-d]

adb shell dumpsys meminfo com.google.android.apps.maps -d

4、重要的显示出来的这些参数都代表什么？

答：不小心点错发出来了，我还没来得及总结呢…………哈哈哈哈等我