Process Terminating Restriction

Applies to AQTime 8.81, last modified on January 18, 2022

Normally, profiling results are generated when the profiled application exits. With several AQTime profilers, a DLL is injected into the address space of the profiled process. This DLL will send accumulated data to AQTime when it is notified that the application has finished, and at this point AQTime generates results.

But it is possible for the application to be terminated without its sending the expected notification. In this case, the DLL may not get a chance to report anything to AQTime - it will be just cleaned out of memory. So, AQTime may not report any results if the application was shut down unexpectedly.

AQTime can handle the profiled application’s termination and automatically generate the results if the application was shut down due to the following reasons:

  • An unhandled exception occurred in the application.

  • The application terminated itself by calling the Windows API TerminateProcess function.

In other cases, for example, when the profiled application is terminated unexpectedly by another application, AQTime does not receive notifications about the application closing and thus does not collect results automatically. The workaround is to ask for early results by using the Run > Get Results menu itemthe AQTime > Get Results menu itemthe AQTime > Get Results menu item. See Getting Results During Profiling.

See Also

Getting Results During Profiling

Highlight search results