Allocation Profiler - Results of the Classes Data Category

Viewing Profiler Results

Specifics of Tracking Classes in Visual Basic, Intel C++ and Borland C++ Applications

Specifics of Tracking Classes in Visual C++, Delphi and C++Builder Applications

Each row in the Report panel shows profiling results for every single class: the total and current number of class instances, their size, etc. (The Report panel columns are described in the Allocation Profiler - Report Panel section.) This gives you a summary view on what happened in the application during profiling (you can also view the summary results in the Summary panel).

The Class Name column in the Report panel serves as the identifier of the class. The possible values are listed in the table below:

The footer of the Report panel column holds summary values for data displayed in that column. For instance, the footer of the Live Size column displays the summary size of all class instances that existed in memory at the moment of results generation. If you select two or more classes in the Report panel, the footer will show the summary values for the selected classes only (for more information on how to select several rows in a panel, see Selecting Several Records in a Panel).

To determine if class instances existed in memory at the moment of results generation, check the Live Count column value. If it is greater than 0, class instances existed. If you profile an unmanaged application and obtain results upon closing the application, non-zero values in the Live Count column help you find memory leaks. To find them quicker, you can sort or filter results in the Live Count column.

AQTime does not report the names of classes in Visual Basic 6.0, Intel C++ and Borland C++ applications. These classes are traced as memory objects, and leaked classes (if any) are included in the following memory classes:

• Visual Basic classes are included in the VB native memory class (see Analyzing Visual Basic Applications).

• Intel C++ and Borland C++ classes are included in the C++ native memory class (see Analyzing Intel C++ and Borland C++ Applications).

• AQTime may or may not trace classes that reside in Visual C++, Delphi and C++Builder applications as memory blocks. In order for AQTime to be able to trace a class, as a class, not as a memory block, the class must meet certain requirements. For a detailed description of these requirements, see the Allocation Profiler - Analyzing C++Builder Applications and Allocation Profiler - Analyzing Delphi Applications topics.

• When working with Visual C++ applications compiled in Debug configuration, the Allocation profiler tracks the actual size of memory blocks allocated by the profiled application. This size (the reported size) can be larger than the size specified in the application’s source code. See Allocation Profiler - Analyzing Visual C++ Applications for more information.