Memory Snapshots 

A memory snapshot contains information about the various data objects and instances of an internal session and their memory consumption. A memory snapshot is stored in a file on the application server in XML format and kept there for a maximum of 4 weeks. The index is determined through the profile parameter DIR_MEMORY_INSPECTOR. Older memory snapshots are automatically deleted, without user dialog. If you wish to keep these memory snapshots, you can have them loaded during display onto the presentation server.

 

Static and Dynamic Memory

In the context of memory consumption, we differentiate between static and dynamic memory.

The static memory contains the data contents of flat data objects and the references of deep data objects (reference variables, strings, and internal tables).

The dynamic memory contains the data contents of deep data objects that are referenced by references in the static memory. These are:

·        Instances of classes that are explicitly referenced by object reference variables

·        Anonymous data objects that are explicitly referenced by data reference variables

·        The data contents of strings that are implicitly referenced by data objects of the data type STRING or XSTRING

·        The data contents of internal tables (table bodies) that are implicitly referenced by data objects declared as internal tables

 

Naming Conventions for Memory Snapshots

The file names are abDbgMemory_XX_YYYY, where XX is the number of the current work process and YYYY is a running numbering within the current work process. The file names are unique as long as the work process is not restarted. After a restart, the system also restarts the count and existing files can be overwritten.

 

Currently open memory snapshots are protected from deletion by the user, but not from being overwritten by the creation of a new memory snapshot. Therefore, if you want to retain a memory snapshot for a longer period, you should save it locally on the presentation server.