SYSTEM_MEMORY_DESTROYED SAP ABAP Runtime Error system memory destroyed

SYSTEM_MEMORY_DESTROYED is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.

Short Dump Classification: I - Internal Kernel Error

You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.

Also check out the Comments section below to view or add related contributions and example screen shots.

SYSTEM_MEMORY_DESTROYED ABAP Runtime Error

Please see dump for more details about the possible cause of this runtime error and how it could be avoided.

Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.

Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.

This short dump contains further information in the form of trace files in the working directory.
These files could be the following: dev_w*, dev_stor, mm.* SAP memory corrupt. Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.

Try to reproduce the error by entering the same data again. Enter /h in the command field to start debugging. Just before the termination, choose 'Settings -> Memory monitoring' in the debugger menu.

If you continue processing by pressing F8, the debugger will try to stop at the line of ABAP code responsible for the error. If operations are performed on Dictionary objects there, the error might be due to an inconsistency between the nametab, the database, and the ABAP load. In this case, activate the relevant table in transaction SE11 and regenerate the ABAP program. One of the SAP memory areas (roll, EM, heap or short memory) has been overwritten. You can usually eliminate the error by using a newer kernel. Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.