Memory Management Settings for Service Interfaces

Allocation control

Non-Shared Memory

No threshold limit

Click this if you do not want the run-time system to restrict the amount of memory available to the application

Allocate at most ... bytes of memory

Specify the amount of memory to allocate to dormant programs in the run-time system. A dormant program is one which has been logically cancelled by the run unit, but has not been physically unloaded from memory. A dormant program can be executed considerably faster than one which has to be loaded from disk, so this memory allocation is effectively a cache of programs that have been cancelled but might be needed again.

When the size you specify is reached, all cancelled programs are unloaded, thereby releasing all of the dynamically allocated memory. If you specify a size of 0, all cancels will physically unload the program from memory.

Strategy

Check bytes

Check this to prepend and append check bytes to each memory allocation.

Equivalent tunable: memory_strategy with check bytes set

Check the last ... free memory blocks

Specify the number of freed memory blocks to monitor for subsequent corruption.

Equivalent tunable: memory_strategy with check freed memory set

Reuse freed memory

Check this if you want to allow freed memory being monitored for corruption to be used to satisfy allocation requests.

Equivalent tunable: memory_strategy with reuse set

Compatibility

Check this to maintain compatibility with previous versions of the run-time system in the way it handles memory allocations.

Equivalent tunable: memory_strategy with reuse set

Validate all memory when allocating and freeing

Check this to validate memory each time an allocation or free operation is performed.

Equivalent tunable: memory_strategy with validate set