The Java Heap Memory Observe Tool (also known as the Heap Walker) records detailed information about the Java heap at a specific point in the virtual machine execution. It collects and displays:
data for all objects (classes, sizes, addresses and references)
addresses for all roots
names of all classes
Please note the following:
The memory profiler uses the same connection technology as the Java debugger(see “On-device Debugging Procedure”). Because they use the same transport layer, the memory profiler and Java debugger cannot be used simultaneously.
Note - For the memory profiler, the Xrunjdwp -suspend option must be set to n.
The memory monitor slows down your application startup because every object created is recorded.
The memory usage you observe with the emulator is not exactly the same as memory usage on a real device. Remember, the emulator does not represent a real device, it is just one possible implementation of its supported APIs.
See also: Run the Java Heap Memory Observe Tool