Bug 45742

GemStone/S 64 Bit

3.2.9,, 3.2.8, 3.2.7, 3.2.6, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2, earlier versions


Risk of SEGV during automatic index update

When an application modifies an instance variable of an object that participates in an index, the index is automatically updated. If this value is a committed object that is not currently in temporary object memory, it is possible for this to SEGV


Avoid conditions in which objects are flushed out of memory.  Using a large cache, and setting GEM_TEMPOBJ_AGGRESSIVE_STUBBING to false, may help avoid issues.

Last updated: 12/16/15