2418582 - Memory is not released completely when returning to the selection screen of a transaction.

Take program /1BCDWB/DBBSEG as an example, assign it to a Z*/Y* transaction code and start the transaction:

1. Display large data volume, after the ALV list is displayed, message "Memory low. Leave the transaction before taking a break!" might be displayed and the process turns into "Back-End Session in PRIV Mode" on hold status in SM50:

2.Double click the process or use Tr.SM04 to check the memory:

   - Double click the process in SM50:

  - Check user memory in SM04:

3. However, after pressed 'F3' and go back to selection screen, it can be observed that the process in SM50 is retained and the used memory doesn't decrease too much(memory is not released completely):

 4. At this stage, when 'execute' button is pressed to display the ALV list again, the memory consumption increases significantly during the second execution with the same selection quantities. Memory dump may happens, TSV_TNEW_PAGE_ALLOC_FAILED.eg

* The problem doesn't happen when /1BCDWB/DBBSEG is started from SE38 directly.

• NW ABAP System.
• S/4HANA System.

F3 back to selection screen, memory process not released, TSV_TNEW_PAGE_ALLOC_FAILED, SE38, transaction, SM04, "Memory low. Leave the transaction before taking a break!" https://me.sap.com/notes/1241185 , KBA , BC-ABA-LA , Syntax, Compiler, Runtime , Problem