What’s New in AQtime 6.20

The Event View panel has new toolbar buttons that help navigate through events that were logged for the same thread.

In AQtime integrated into Microsoft Visual Studio 2005 and 2008, links in the “Top 10 uncovered routines” section of the Light Coverage Profiler results summary did not work.

AQtime could hang if profiling started right after the project had been opened.

If you were profiling a native application that launched a .NET application and then you pressed Get Results, the .NET application could crash.

If you selected the Add Assembly command in the Setup panel, it was impossible to abort reading the GAC until the Add Assembly to Project dialog was shown.

AQtime crashed if the AQtime x64 Service was not installed.

AQtime did not launch Internet Explorer while starting profiling after switching actions.

AQtime worked slowly while working with a great number of files that were located on another computer on a local network.

AQtime could not continue profiling an application if a dump was generated on pause.

AQtime crashed while printing documents if the list of installed printers was changed.

Some AQtime modules had incorrect version information.

AQtime could crash upon loading incorrect module files.

The layout of the Details panel’s columns was not saved between sessions.

During the installation process, AQtime checked for the needed version of Microsoft Script Debugger improperly.

Detection of AQtime 5 integrated into Microsoft Visual Studio, Borland Developer Studio and CodeGear RAD Studio by the AQtime 6 installation program has been improved.

AQtime could not detect the creation of certain objects when profiling Delphi 2009 applications.

A Visual C++ application could crash during profiling under the Allocation profiler if the Fill released memory blocks option was enabled.

The Allocation profiler did not detect leaks in VCL C++Builder applications created with CodeGear RAD Studio 2009.

A new standard CRT leak was registered in AQtime and was excluded from profiling results.

While profiling under the Allocation profiler, Delphi 7 applications having the ADOConnection component crashed when the component got connected.

A leak produced by the ShellExecuteEx function was not detected by AQtime.

Some GDI+ resources were reported as non-released even if they were released.

The Creation Call Stack pane of the Allocation profiler result details lacked the Unit Name column.

The "n" specifier could not be used for the Time column that displayed results in machine cycles.

While viewing the Performance profiler results, the Display Next and Display Previous buttons of the Report toolbar worked incorrectly.

The context menu of the Report panel did not allow you to add routines from results to profiling areas, triggers and actions, if there were no areas, triggers or actions defined in the project.

AQtime displayed erroneous messages when you added script files to your AQtime project on a 64-bit version of Windows.

Internet Explorer could hang during script profiling.

Performance profiling results for web scripts could include garbage information.

AQtime could display incorrect results of script profiling.

In certain cases, AQtime could ignore profiling areas, triggers and actions when profiling scripts.

On some computers, AQtime showed no information on routines while profiling VBScript code.

If the Profile Entire Script Code By Routines option was enabled, AQtime couldn’t profile TestComplete 6 scripts.

The Editor did not display the source code of the HTML file that was added to the project with the Add URL command.

Sometimes, the Editor panel was not updated completely, and some markers were not drawn.

The Editor did not highlight syntax elements of HTML files.

In certain cases, the Editor displayed incorrect source code for the selected script routines.

AQtime could hang when the Editor was displaying HTML code.

The Editor kept highlighting a user keyword after it had been removed.

The Editor panel used improper syntax color highlighting for .c files.

The Event View panel showed exit codes only in decimal format. Now it also shows them in hexadecimal format.

Some of the Event View commands had no icon.