doesNotUnderstand can corrupt stack
There is a very small timing window during which the running of not connected
set GC during execution of a doesNotUnderstand method can cause stack
corruption. This is often exhibited as another #rtErrDoesNotUnderstand
error during execution of the doesNotUnderstand method.
In practice this error is extreamly rare, and is only exposed in applications
that make frequent use of doesNotUnderstand and have frequent occurrences of
not connected set GC.
Recode application to minimize use of doesNotUnderstand, and/or reduce
the possibility of not connected set GC. Ways of reducing not connected
set GC include:
1. If possible, decrease the number of temporary objects generated during
a single transaction.
2. Increase the size of the gem's temporary object cache via
3. Increase the settings for GEM_NOT_CONNECTED_THRESHOLD and