Hi Sagar
The better option is to determine what object (class instances, internal tables etc.) is allocating the memory.
This can be done in debugging mode. Go into debug shortly before you expect the shortdump.
With the new debugger the memory consumption is not visible as default. Create a "New Tool" in one of your tabs. In the "New Tool" popup choose "Special Tools: Memory analysis". Within the new sub-screen click the second Icon from the top to get a list of memory allocating objects (sorted by size).
For all the larger objets in the list try to find a way to clear/refresh the objects after each Logical Unit of Work (LUW).
Yep
Jürgen
