In longer-running Purify'd programs, you can generate a new memory leaks summary while the program is running by using the new leaks button.
For example, if you are testing an X Windows word-processing program you can:
Start the program.
Click the new leaks button. (At this point, Purify might report that there are no new leaks.)
Perform some action with the program. For example, open a document.
Click the new leaks button again. If Purify reports new leaks at this point, you know that they occurred in the document-opening phase of your program.
In this way, you can isolate memory leaks that occur in a complex program.
The new leaks button can generate a leak summary only when a program is running, not while it is stopped in the debugger. To get a new leaks summary from the debugger, call the purify_new_leaks function directly from the debugger.