The VMMap Window
When you run VMMap, it will present a process selection dialog. After you select a process it analyzes the process and presents the graphs:
Commit Summary Graph This graph shows the committed (memory that represents data or code) memory usage of the process by type. The graph's scale is the total committed virtual memory usage of the process.
Private Summary Graph This graph shows the committed private virtual memory. This memory is backed by the paging file and charged against the system commit limit. It corresponds to the PrivateBytes performance counter.
Working Set Summary Graph This graph shows the working set usage of the process by memory type. Working set represents the amount of commited virtual memory that's in physical memory and owned by the process. The graph's scale is the total committed virtual memory.
The color key for the regions in the graphs is presented in the Summary View. Below the graphs VMMap shows two windows:
Summary View This shows a summary of the virtual and physical usage of the process by type.
Details View This shows the memory regions of the process address space.
For each region, VMMap displays the memory type, memory protection, and virtual and physical memory usage. Selecting a type in the Summary View filters the Details View to just show regions of the selected type. Select Total to show all memory types in the Details View. In order to reduce noise in the output, VMMap does not show entries that have a value of 0.
Both windows include the following columns of information:
Total size of the allocated type or region. For the Summary View and regions in the Details View that do not have reserved areas, this is equal to the maximum amount of physical memory required to store the region's data.
The amount of the allocation backed by system virtual memory (RAM and paging files) and charged against the system commit limit.
The amount of the allocation that, if modified, is private to the process (copy-on-write pages that have not been modified are included). This represents the charge to the system commit limit (sum of RAM plus the paging files) of the region.
The amount of physical memory assigned to the type or region.
The amount of physical memory assigned to the type or region that cannot be shared with other processes.
The amount of physical memory assigned to the type or region that can be shared with other processes.
The amount of Shareable WS that is currently shared with other processes.
The amount of the working set that is locked into physical memory. This corresponds to memory locked via the VirtualAlloc API as well as Address Windowing Extensions (AWE) memory views. Note that working set figures returned by some other diagnostic tools does not include AWE memory.
Largest The largest block of the particular size.
Note: Because of limitations in the APIs provided by the operating system, on 64-bit Windows XP or 64-bit Windows Server 2003, Vmmap does not show the regions corresponding to 32-bit thread stacks when analyzing 32-bit processes.