For Partners

What’s New in AQtime 6.21

AQtime could crash while working with a project located in a network folder if the network connection went off.
AQtime x64 could crash when generating a dump file for a 64-bit application.
AQtime didn’t catch debug strings generated by Visual C# applications created in Microsoft Visual Studio .NET 2002.
The Exclude Standard Files option didn’t filter out standard units of unmanaged Visual C++ applications.
AQtime couldn’t read debug information from URLs.
AQtime didn’t load debug information for modules added by using file:///path URLs.
In 64-bit versions of the Windows Vista operating system, the column list next to the Show critical path for column option remained disabled after the option was turned on.
If a routine did not contain information on the source file, the Report panel displayed an empty string in the Source File column. Now this column contains the <No Source File> entry to avoid confusion.
AQtime crashed if the Ins key was pressed in the Explorer panel while no project was open.
AQtime couldn’t start on Windows NT SP6.
A meaningless error message was displayed when trying to run AQtime on an unsupported processor. Now the message describes the reason of the error more clearly.

The profiled application could crash during profiling under the Allocation profiler if custom profiling options were used.
The profiled application could crash during profiling under the Allocation profiler if the Check memory bounds option was turned on.
An access violation could occur while profiling a dynamically linked library under the Allocation profiler in IIS mode with the Check Memory Bounds option turned on.
Allocation profiler results could include incorrect object addresses if the application was profiled with the Check memory bounds option turned on.
An error could occur when viewing the Classes Data results of the Allocation profiler if the Check memory bounds option was enabled during profiling.
When profiling Borland C++ Builder 2007 applications, some memory leaks were not detected for objects other than TObject descendants.

The profiled application could crash when being profiled under the Resource profiler with the Collect stack information option set to None, and the Resource categories to check option set to COM Resources.
AQtime could hang upon starting profiling a .NET Framework 1.1 application with the Resource profiler.

The profiled application could crash on attempts to attach to its process with a dynamic profiler when the Use extended debugger for managed code option was enabled.
AQtime could crash upon starting profiling a Visual C# 2002 application with the Exception Trace profiler.
A WCF service crashed when being profiled under all but the Exception Trace profiler.
The BDE SQL profiler could generate incorrect results for CodeGear Delphi and C++Builder 2009 applications.
When the Profile Entire Script Code by Routines option was set, the Light Coverage profiler still profiled scripts by lines.
When profiling a script with the Coverage profiler, the results of the Source Files and Modules categories erroneously reported that zero percent was covered, even if the routines of these files and modules were called.
AQtime crashed during static analysis of SQLite’s sqlite3.dll library.

In certain cases, the Editor didn’t display the source code of elements with known debug info.
AQtime did not reload modified source files of the profiled modules.
The Editor panel didn’t offer to specify project search directories for an unmanaged Visual C++ 2005 application if it could not find some of its source files.
By default, the Editor displayed all available comments with profiling results in the code of profiled routines, which could clutter up the source code.
The contents of the Editor panel were not refreshed after comment customization.
When switching to Editor from the Setup panel, the position within the code was chosen incorrectly.
Sometimes, the gutter of the Editor panel disappeared.
It was possible to delete syntax elements in the Editor’s Highlighting settings.

Microsoft Visual Studio 2005 and 2008 could hang after opening AQtime projects
AQtime integrated into Microsoft Visual Studio 2003 could hang when comparing profiling results
Sometimes, AQtime integrated into CodeGear Delphi 2007 could not find source files even if the Project Search Directories were specified
AQtime integrated into Borland Developer Studio 2006 could crash upon getting profiling results
AQtime integrated into Borland Developer Studio 2006 could crash on exit.
Borland Developer Studio 2006 with AQtime integrated into it could hang on exit.

The Script Profiling Support feature was installed incorrectly if it had been removed before.
AQtime’s installation program failed to register the DebuggerEngine.dll module on Windows 2000.