Using the Memory Object Explorer in the New ABAP Debugger

Use

With the Memory Object Explorer, you can see how memory objects are related to each other in the program that you are debugging.

The memory objects in a program are linked to each other to form a network or graph. At the top level are memory objects referenced by variables of the program that is executing. These objects may have variables or attributes that reference other memory objects. Subordinate objects, in turn, may reference other memory objects.

Figure 1: Navigating in the Memory Object Explorer

The Memory Object Explorer lets you navigate in the graph of memory objects. You start from any variable that is in use in the program that you are currently debugging. You can then use the Memory Explorer to do the following:

Navigate 'upward' from the memory object to see its superior objects. These are variables that reference the memory object.
Navigate 'downward' from the memory object to see its subordinate objects. The object in focus contains attributes or variables that reference the subordinate objects.
Display the contents of any memory object. For example, you can see the lines in an internal table or the attributes in an instance of an ABAP class.

Starting the Memory Objects Explorer

To start the Memory Analysis tool from the initial screen of the New ABAP Debugger, do the following:

From the tool bar at the right side of one of the debugger windows, choose Replace Tool.
In the popup which follows, open Memory Management.
Choose Memory Object Explorer.

Following References with the Memory Object Explorer

The Memory Object Explorer is the best Memory Analysis tool for follow references from one memory object to another,

When the amount of memory in use in your program changes and you don't understand why or how the change has occurred, it is often necessary to follow the references between memory objects to see how they are being shared, which variables hold references to each object, and what contents each memory object holds.

For example, jumps in memory use often occur when a shared value-semantic object such as an internal table becomes unshared. In order to understand where and how the shared memory object needed to be copied, you may need to analyze the references in the memory objects graph in depth.

Figure 2: Full Visibility of References in the Memory Object Explorer

It is easiest to see the advantages of the Memory Object Explorer for tracking references and seeing how the graph of memory objects changes if you compare it to other tools:

The Memory Object Explorer differs from the Dominator Tree view because it lets you navigate in the complete graph of memory objects.

The Dominator Tree constructs hierarchies only to show exclusive references from a superior object to a bound subordinate object. All other objects appear simply as top-level memory objects, which does not help you to see or understand the network of memory references.
The Memory Object Explorer differs from the Memory Objects list because Memory Objects lists all memory objects as if they were on a single hierarchical level.

The list shows references to each object, but if you want to understand the graph or network of memory objects, then you must track the references from object to object by hand.