The new leaks button searches for memory leaks in your application as it is running.
The button invokes the Purify API function purify_new_leaks() in your application by sending a signal. The signal is hidden from your application, but may interrupt slow system calls (read, write, select, sleep), causing them not to set errno to EINTR. If your application is not designed to handle interrupted system calls, this may result in unexpected behavior.
Notes:
Purify's memory leaked summary message reports leaks when the application has exited.
See also Using the new leaks button.