Defrag Tools: #7 - VMMap

Play Defrag Tools: #7 - VMMap
Sign in to queue


In this episode of Defrag Tools, Andrew and I walk you through Sysinternals VMMap. VMMap allows you to see how the Virtual Memory of a process is being used. You can see how much is used, for what purpose it is being used, and if there has been any memory leaks. Like last week with RAMMap, we cover some Memory Management theory to understand the data in VMMap.

Sysinternals VMMap
'Mysteries of Memory Management Revealed' talk [Part 1, Part 2]
Sysinternals Administrator's Reference - [Amazon]

[01:32] - Bar Graphs
[02:58] - Committed, Reserved or Free
[03:35] - Shared Memory and Copy on Write
[05:35] - Memory Types
[09:06] - CPU Addressing Limit (~44bits)
[10:17] - Manual Refresh (F5) and Difference (Ctrl-D)
[11:49] - 'Image' entries
[14:55] - Menus
[17:33] - Timeline... First look
[18:30] - Symbols
[19:30] - Tracing an application from launch
[21:19] - Timeline... Second look
[22:58] - Tracing an application from launch (2nd attempt)
[24:15] - Application Symbol and Source Paths
[25:50] - Source code from a Stack
[27:07] - Summary



Right click to download this episode

The Discussion

  • User profile image

    Hey Andrew, Where did you get that great t-shirt ?

  • User profile image

    @Roger: They all come from the Microsoft Company Store (the shop on Redmond campus, as opposed to the retail shops we now have). You'll have to come visit campus!

  • User profile image

    Excellent presentation, I was using the vmmap earlier today to troubleshoot a memory leak issue and was overwhelmed with the stats. This makes it clear. Thank you!

  • User profile image


    I understand the Heap Allocations button should allow me to see call stacks, but the button is always disabled (grayed out) no matter what I try. (I used the "Launch and Trace New Process" feature to run my application, but it doesn't help.)


Add Your 2 Cents