Handling Failed Memory Assertions
If a memory assertion has identified one or more instances as potential memory leaks, a dialog box will be brought up that informs you about the failed assertions and allows you to decide on actions to perform.
The information presented for a failed assertion includes the failed assertion method, the call stack of the assertion, and the instances that have been identified as potential memory leaks by the assertion. For more information about the presentation of memory assertions, see Viewing Failed Memory Assertions.
In the dialog box, there are two actions that can be performed after the memory assertion has failed:
• Collect a full heap snapshot
If this option is checked, a full heap snapshot will be collected when OK is clicked. A full snapshot has to be collected in order for the profiler to present information about the potential memory leak instances.
• Stop the profiling session
If this option is selected, the profiling session will be ended when OK is clicked, after the full heap snapshot has been collected (if requested).
NOTE! If the profiler is running in non-interactive mode and Perform default actions is selected for memory leak detection, then no dialog box will appear when a memory assertion has failed.
Viewing Failed Memory
Assertions