Bug 51076

GemStone/S 64 Bit

3.7.1, 3.7, 3.6.8, 3.6.7, 3.6.6, 3.6.5, 3.6.4, 3.6.3, 3.6.2, 3.6.1, 3.6, 3.5.8, 3.5.7, 3.5.6, 3.5.5, 3.5.4, 3.5.3, 3.5.2, 3.5.1, 3.5, 3.4.5, 3.4.4, 3.4.3, 3.4.2, 3.4.1, 3.4, 3.3.9, 3.3.8, 3.3.7, 3.3.6, 3.3.5, 3.3.4, 3.3.3, 3.3.1, 3.3, 3.2.16, 3.2.15, 3.2.14, 3.2.13, 3.2.12, 3.2.x, 3.2, 3.1.x, 3.x, 2.4.8, 2.4.4.8, 2.4.4.7, 2.2.6.5, 2.x

AlmostOutOfMemory handlers not effective if needed while in primitive

Defining exception handlers for AlmostOutOfMemory or AlmostOutOfMemoryError allows you to catch conditions in which your Gem would otherwise run out of temporary object memory and exit, and perform some actions to make more memory available.

However, if the operation that requires more memory than is currently available occurs when the code is executing in a primitive call, the AlmostOutOfMemory handlers cannot intercept the exception and take action to avoid an exit with out of memory.

Workaround

Avoid executing single primitive operations that will require significant amounts of memory; breaking these up will return control to where the AlmostOutOfMemory handler can free up memory.


                

Last updated: 8/9/24