If the Classes Data category is selected in the Explorer panel, the Report panel displays a list of classes that were created during the application execution. If the Live Count column value is not zero for some class, this means that some of the class instances were not released.
When you select a class for which the Live Count column value is not zero, the Children pane of the Call Tree panel displays the hierarchy of function calls that led to the creation of a class instance. The Parents pane of the Call Tree panel is actually not used.
|The Call Tree panel displays information only if the View Allocation Paths in Call Tree button is pressed on the Report toolbar.|
The Call Tree panel displays information in the following columns:
|Columns (in alphabetical order)||Description|
|Class Name||The name of the object class containing the routine.|
|Live Count||The number of class instances created by the routine. If the C++ native memory, VCL native memory or VB native memory class is selected in the Report panel, this column contains the number of memory blocks that are allocated by the appropriate routine. For the Memory Overwrite Error row, the column value specifies the number of memory block violations that were detected.|
|Live Count with Children||The total number of class instances or allocated memory blocks that existed in memory after the routine was called (including the instances created by child routines).|
|Live Size||The size of class instances or memory blocks (in bytes) that are created or allocated by the corresponding routine. Note that the amount of allocated memory shown in AQTime may differ from the amount of memory shown for your application in the Task Manager. See a note about this in the description of the Allocation Profiler. For the Memory Overwrite Error row, the column value specifies the size of all memory blocks whose bounds were violated.|
|Live Size with Children||The total size of class instances or memory blocks (in bytes) that existed in memory after the routine was called (including the size of the instances created by child routines).|
|Module Name||The name of the module containing the routine.|
|Routine Name||The name of the routine.|
|Source File||The name of the source file for the routine. The values for this column are read from the application’s debug info. If the debug info does not contain information on the file name, the column is empty.|
|Source Line||If the stack information is collected by routines during the profiling (that is, if the Routines only option corresponding to the desired stack area is selected), the column specifies the number of the source code line where the routine’s implementation begins.
If the Collect info about lines option that corresponds to the desired stack area is selected, the column specifies the number of the source code line where the method that creates or deletes an object reference was called.
The values for this column are read from the application’s debug info. If the debug info does not contain information on the file name, the column is empty.
|Unit Name||The name of the unit that stores the routine’s code.|