Memory Validator - Hotspot

Your program may not leak memory but you may have parts of your program that allocate more memory than you realize. By identifying such areas you can focus on managing these allocations in a more structured way. By doing so you can reduce the amount of time your program spends in the heap manager, reduce memory fragmentation, and increase the speed at which your program executes. The allocations are displayed in a tree format, which can be expanded to show where sub-allocations in the hotspot occur. Each branch expands to a source code fragment. As with the other views, the stack trace can be viewed in a tree format and the source code can be viewed as a fragment or edited as appropriate.

This view provides that ability to specify which type of allocation you are interested in:- CRT (new/delete/malloc/free etc), HeapAlloc, LocalAlloc, GlobalAlloc, VirtualAlloc, Handles and User Managed memory.

This picture shows an expanded hotspot view showing the different locations that make up one of the allocation hotspots.

Click the picture for a larger image.