Before NetWeaver 7.0 EHP2, it used to be difficult to analyze memory problems that were really specific to an ABAP Web Dynpro application and not just related to some mammoth internal table deep down in the application logic.
The problem was that it was hard to see the forest for the trees in the Memory Objects ranking lists:
- What objects belong to the ABAP Web Dynpro runtime?
- What objects belong to the Web Dynpro application?
- What belongs to the backend infrastructure?
The old memory analysis functions could not tell the difference between one type of object and another.
Here’s an example:
In the New ABAP Debugger, the application-specific memory analysis tool for ABAP Web Dynpro brings some order to the situation and lets you analyze the memory consumption of your ABAP Web Dynpro application much more easily and efficiently.
There is also an extra filter option that lets you hide memory objects that do not pertain to the Web Dynpro application and runtime. In this case, that includes objects that belong to the ESI framework (web service infrastructure). Here, you can see the effect of the filter – it lets you concentrate exclusively on memory objects that belong to ABAP Web Dynpro.