Scripting languages have a lot in common with ordinary programming languages, the main peculiarity of scripts is that they're not compiled into an executable and they require another host application to run a script.
AQtime can profile scripts executed by the Microsoft Scripting Engine which is used in Internet Explorer, Windows Script Host, TestComplete and many other applications. When the host application is being profiled, AQtime recognizes script actions and gathers data from them. Afterwards, the results of the script execution are reported along with the host application’s results.
AQtime 6 reintroduces the Reference Count profiler that is intended to monitor object references. Early stages of this profiler first appeared in AQtime 3, but it was not included in later versions of the tool. Unlike its forerunner, the new profiler allows you to trace references not only to VCL objects, but also to any objects that implement the IUnknown interface or its descendants (for instance, any COM object). The profiler tracks the AddRef and Release methods that create and delete object references. By analyzing this information you can locate the objects that have unreleased references as well as the objects that were released prematurely.
The functionality of one of the most frequently used profilers, the Allocation profiler, has been extended. Now, it allows you to reveal situations when memory blocks are used after they have been de-allocated, that is, the so-called use after free situations. These situations are hazardous and may lead to access violations, crashes or unpredictable behavior.
The built-in .NET debugger now collects more information. Now, it is possible to obtain call stacks of .NET functions, display user-defined names of CLR threads and trace specific .NET events.
AQtime can now generate profiling results even if the application was terminated by the TerminateProcess function or crashed due to an unhandled exception. Thus, you can successfully profile even unstable applications.
This version introduces a simplified version of the Coverage profiler called Light Coverage. Its main purpose is to show whether a routine or line was executed or not. It does not collect information about the amount of times a routine (line) was executed and does not divide routines (lines) by threads. As a result, the profiler works much faster. Another benefit is that the profiler results are merged quicker and are not divided by threads.
The BDE SQL profiler times the execution of SQL queries and stored procedures called through the Borland Database Engine. This profiler appeared in AQtime 3, but later, it was replaced with the Performance profiler. However, it turned out that the universal Performance profiler was not as good as the special-purpose profiler. That is why AQtime 6 reintroduces the BDE SQL profiler while keeping the abilities of the Performance profiler.
AQtime's integration with the most recent version of Visual Studio allows you to create Team System test items. Thus you can extend your test collections with specific AQtime tests. Read Integration into Microsoft Visual Studio Team System for more information.
Many integrated development environments include their own standard units in your application. These units perform a lot of auxiliary tasks, interact with classes and controls, draw forms, and so on. However, generally, those units cannot be modified since their source code is not available, and therefore standard units are not worth profiling. To concentrate on the source code of your application, you can enable AQtime's Exclude standard units option that hides standard units in the Modules pane. If this option is enabled, profiling results are not generated for standard units.
AQtime now exports profiling results to a database. The results displayed in the Report, Details, Event View, Call Tree and other panels, as well as the application’s debug information can be exported. A vast amount of database formats is supported. Using this feature you can create a storage where all of the profiling results are stored and you can access the results from another application or process the results.
The Resource profiler can now monitor allocation and usage of resources created with the GDI+ class-based API. This API is a successor of the Graphics Device Interface (GDI) and is widely used in Windows-based applications. The GDI+ library is included in Windows XP and Windows Server 2003, but can also be used on the Microsoft Windows NT 4.0 SP6, Windows 2000, Windows 98, and Windows Millennium operating systems.
The GDI+ library functions are traced by the Resource profiler if the GDI+ Resources category is selected in the Resource categories to check option.