The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed. Resolved: Release in which this issue/RFE has been resolved. Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
Recent testing of CMS w/tightened lock assertion checking revealed
that we may be vulnerable to a race when expanding a CMS generation.
Comments
EVALUATION
This was revealed from a tightened assertion. It turns out that the tightened assertion
was much too strong. So this was not a bug per se, but an assertion that was made too
tight. The assertion has now been fixed, and the fix will be checked in as part of the
cleanup done in the fragmentation related bug covered in 6631166 (and 6755514). I'll close
this bug as a duplicate of 6755514 (and 6631166) for that reason only.
29-10-2008
WORK AROUND
Fixing the size of CMS generations works around the bug:
-Xms == -Xmx *and* -XX:PermSize == -XX:MaxPermSize