Risk of repository corruption if OopNumberHighWaterMark grows by more than 50M objects during MFC
When the OopNumberHighWaterMark grows by a very large amount (more than 50M objects) during MFC, there is a risk that the repository can be corrupted. Internal structures need to be resized in this case, and the resize was not applied correctly. This may cause SEGV, in which case the repository is not corrupted; but depending on the specifics of the occurrence, OOPs may be handled incorrectly and so introduce corruption.
If the growth occurs between aborts of the MFC, then the MFC will report an error "oopHighWater grew more than expected", which is what occurs in all cases in releases earlier than 3.2.
Workaround
Ensure that your repository does not have a very large amount of growth during MFC.
Last updated: 3/19/15