Task 9: Seeing Leaks
The Leak reports are essentially the same as the Heap Status Source and Heap Status Backtrace reports. Honing in on the information you want is simpler in these reports as there are fewer controls and less data. For example, there is no Data Source area. The real difference between a Heap Status Source report and a Leak Source report is that a Leak Source report does not show allocations that are not leaked. That is, these two reports focus only on leaked memory.
As using these Leak reports is identical to using Heap Status reports, see Task 8: “Obtaining Detailed Heap Information”.
Table 10: Filtering Reports
The amount of information displayed in a Leak Detection or Heap Status report can be considerable. In addition, this information includes memory blocks allocated within all libraries, shared or otherwise, that your program uses. In other cases, your program may be allocating memory in many different ways, and you want to focus on only a few of them. This task shows you how to use filters to eliminate information from reports.
Before reading this task, you should be familiar with the following information:
Chapter 1, “Locating Memory Problems”
An overview of memory concepts and MemoryScape.
Task 1: “Getting Started”
How to start MemoryScape with a summary of the kinds of information you can ­obtain.
Task 3: “­Setting MemoryScape Options”
How to configure MemoryScape so that it performs the activities you want it to perform.
Task 4: “Controlling Program Execution”
How to start and stop program execution.
Creating Reports

How to create reports, discussed in the introduction to this chapter (“Memory Tasks”).
When filtering is enabled, MemoryScape considers each enabled filter and applies it to the report’s data. Filters can have any number of actions associated with them. Enable a filter by selecting the check box at the top of a report.
Topics in this task are:
• “Adding, Deleting, Enabling and Disabling Filters”
• “Where to Go Next”