Records all memory requests, including calls to malloc(), realloc(), and other calls to your malloc library. It also includes calls to C++ operators such as new and delete that indirectly use this library. It can even include memory management functions performed by some Fortran libraries.

When you ask for a report, MemoryScape analyzes this recorded information and displays the information you request.

This selection also sets automatic event notification.

In most cases, Low is all you’ll ever need.

In addition to performing all operations indicated by Low, MemoryScape writes guard blocks before and after allocated memory blocks. For more information on guard blocks and locating corrupted memory, see Task 11: “Viewing Corrupted Memory”.

This setting increases the size of the allocated memory block, but the extra overhead is small.

Select Medium only when you need to check for corrupted memory.

In addition to performing all operations indicated by the Low level, MemoryScape writes a Red Zone after the allocated memory block and notifies you if you access memory in this Red Zone. This is called an overrun.

In this case, the additional allocated memory can result in significant extra overhead.

Select High only if you need to check for memory overruns. As an alternative, select Low and use the Red Zones button on the task bar to turn on Red Zones as needed for suspect allocations.

To find underruns in your allocated memory, see “Use Red Zones to find memory access violations”.

In addition to performing all operations indicated by the Low, Medium, and High levels, MemoryScape paints allocated and deallocated memory as well as hoard memory.

These activities both decrease performance and use more memory. For information on when to use these features, see Task 15: “Hoarding Deallocated Memory” and Task 16: “Painting Memory”.

Select Extreme only if you need hoarding and painting.