Updated: October 20, 2013
Applies To: Windows 8, Windows 8.1
Writes a text file containing the following information in tabular form based on the output file specified by
Alloc size, in KB
Out size, in KB
Extents size, in KB
Out Ext size, in KB
-a heap [-pid <processId>] [-stacks] [-frames] [-images] [-range T1 T2] [-lifetime T1 T2] [-size S1 S2] [-cullframes Frame1 Frame2 ... FrameN] [-requireframes Frame1 Frame2 ... FrameN] [-cullLists cullfuncs.txt] [-top <n>] [-totals]
- -pid <processId>
- Shows statistics only for the specified process identifier. If not specified, shows statistics for all processes.
- -stacks [s [o|oc|t|tc|rc]]
- Displays the allocations, aggregated by stacks. This is the default behavior. Sorts by outstanding size (so), outstanding count (soc, total size (st), reallocation count (src, and total count (stc). The default is so.
- -frames [s [o|oc|t|tc|rc]]
-stacks, but the aggregation is by top stack frame, instead of by the entire stack.
-frames, but the aggregation is by image name of the top stack frame.
- -range T1 T2
- Use event data from times T1 through T2, both in microseconds.
- -lifetime T1 T2
- Include only allocations with a lifetime, in microseconds, greater than or equal to T1 and less than T2.
- -size S1 S2
- Include only allocations of sizes greater than or equal to S1 and less than S2, in bytes.
- -cullframes Frame1 Frame2 … FrameN
Removes any top stack frames from the report that match any of the specified frames. The parameter format is
[image!][symbol]. The names are not case-sensitive.
- -requireframes Frame1 Frame2 … FrameN
Requires that each stack have at least one frame that matches at least one of the specified frames. This test occurs before any explicit frame culling with
- -cullLists <fileName>
Frames in the specified file are to be excluded from the result. If a stack does not include such a frame, the stack is excluded. Frames have the same format as for
-cullFrames. The names are not case-sensitive.
- -top <n>
- Limits the number of allocations displayed.
- Displays only the totals of the allocation events.
This action can take several minutes to complete on a large trace due to the heavy sorting and matching performed.
For information on how to capture heap data, see Enabling Heap Data Capture