diff --git a/docs/html/tools/debugging/debugging-memory.jd b/docs/html/tools/debugging/debugging-memory.jd index 0454293e2d440..a7f443c8524e7 100644 --- a/docs/html/tools/debugging/debugging-memory.jd +++ b/docs/html/tools/debugging/debugging-memory.jd @@ -181,11 +181,18 @@ Moving that object into a global member is a simple fix that helps improve perfo

Viewing Overall Memory Allocations

-

For further analysis, you may want to observe how that your app's memory is -divided between different categories, which you can do with the adb meminfo data.

+

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:

-

When talking about how much RAM your app is using with this data, the key metrics -discussed below are:

+
+adb shell dumpsys meminfo <package_name>
+
+ +

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
@@ -210,15 +217,9 @@ determine the actual memory being used by all processes. This means PSS is a goo actual RAM weight of a process and for comparison against the RAM use of other processes and the total available RAM.

-

You can look at the memory use of your app (measured in kilobytes) with the -following adb command:

- -
-adb shell dumpsys meminfo <package_name>
-

For example, below is the the output for Gmail’s process on a tablet device. There is a lot of -information here, but key points for discussion are highlighted in different colors.

+information here, but key points for discussion are listed below.

Note: The information you see may vary slightly from what is shown here, as some details of the output differ across platform versions.