Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
Showing results for 
Search instead for 
Did you mean: 

Page alloc failed - ShortDump

Former Member
0 Kudos

Hi all,

I get dump:


Short text

No more storage space available for extending an internal table.

What happened?

You attempted to extend an internal table, but the required space was

not available.


Error analysis


T_GRID\DATA=L_T_TREE_OUT" could not be further extended. To enable

error handling, the table had to be delete before this log was written.

As a result, the table is displayed further down or, if you branch to

the ABAP Debugger, with 0 rows.

At the time of the termination, the following data was determined for

the relevant internal table:

Memory location: "Session memory"

Row width: 22904

Number of rows: 0

Allocated rows: 1

Newly requested rows: 14584 (in 14584 blocks)


How to correct the error

The amount of storage space (in bytes) filled at termination time was:

Roll area...................... 6221152

Extended memory (EM)........... 2002747344

Assigned memory (HEAP)......... 1000373952

Short area..................... " "

Paging area.................... 147456

Maximum address space.......... 4294967295


Memory consumption

Roll.... 6221152

EM...... 2002747344

Heap.... 1000373952

Page.... 147456

MM Used. 2907678368

MM Free. 90676456

I was trying o check which parameteres I should modify, but the opinions are shared over the net.

Maybe you can suggest something so that I can avoid this dump?

Thank you,



Active Contributor
0 Kudos

This program used 3 GB of memory and was then stopped by the memory parameter settings. Before extending these parameters (if at all possible given the available hardware) you should try to reduce memory usage of the program. If it is a customer own program, try looking at block processing (search for available info) for example, or limit the selection range that users can input. If it is a standard SAP program, look for applicable SAP notes.


0 Kudos

Hello Daniel,

looks like a project reporting in SAP Solution Manager. You are trying to display a table in the ALV grid, that it very large.

Here is most probably the coding where it dumps:

  • first check if there's at least 1 short text.

l_t_tree_out[] = a_t_tree_out[].

SORT l_t_tree_out BY comp_stext DESCENDING.

READ TABLE l_t_tree_out INTO l_l_tree_out INDEX 1.

IF l_l_tree_out-comp_stext NE space.

The idea of this coding is to check if there is an entry in a_t_tree_out[] with the field comp_stext not equal to space.

This task can be easily performed in another way without expensive sort and copying of the table that requires a lot of additional memory space:

LOOP AT a_t_tree_out INTO l_l_tree_out WHERE comp_stext NE space.



If the result of the loop is SY-SUBRC = 0, then there was an entry in the table where short text was not space.

Please create a customer message in the component SV-SMG-IMP and mention there your short dump and copy this reply.

SAP development should fix this programming error with the official note.



Edited by: Yuri Ziryukin on Dec 12, 2011 10:57 AM

Former Member
0 Kudos

Hi Daniel,

Please increase the abap/heap_area_nondia = 8000000000.

and again monitor the same.

Edited by: Parupelly on Dec 19, 2011 1:27 PM