Immortal Memory

These memory areas are referred to as scoped and immortal memory.

You need to be aware of your program's behavior and adjust the size of immortal memory appropriately.

The advantage of this approach is that you can write standard Java code and every new operation will create an object in immortal memory.

Objects allocated in the immortal memory area are accessible to all threads and are never collected.

To ensure the integrity of the heap and the immortal memory area, the RTSJ defines rules for using scoped memory.

We know that immortal memory is never recovered, so we cannot keep creating Measurement objects at will because we would run out of memory.

Before we can apply scoped and immortal memory to our design, we need to understand a little more about how they work.

Immortal memory leaks are a common source of errors in RT Java applications.

Having discounted the heap and scopes, we are left with immortal memory.

NHRTs must create their objects using scoped or immortal memory.

Immortal memory is a resource required by the RTSJ that is not subject to GC.

Because it is never collected, immortal memory is a limited resource that must be used carefully.

Our choice is restricted to some combination of scoped and immortal memory.