-
Bug
-
Resolution: Fixed
-
P3
-
5.0u6
-
b01
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2129493 | 1.4.2_12 | Abhijit Saha | P3 | Resolved | Fixed | b01 |
locking in CMSPermGen::mem_allocate(). These were fixed in Mustang
under 6316605. This bug is being created to allow a backport
of that subset to 1.5.0 and 1.4.2 update trains.
See the suggested fix section of 6316605 for more details.
- backported by
-
JDK-2129493 Incorrect locking in CMSPermGen::mem_allocate()
- Resolved
- relates to
-
JDK-6319671 CMS should use Heap_lock for protecting heap resizing, instead of CMS token
- Resolved
-
JDK-6325682 VM lockup with -XX:+UseConcMarkSweepGC while loading classes with custom classloader
- Closed
-
JDK-6316605 atg server crashed with CMS collector
- Closed
-
JDK-6263371 SEGV in MarkFromRootsClosure::scanOopsInOop
- Closed
-
JDK-2129692 CMS should use Heap_lock for protecting heap resizing, instead of CMS token
- Resolved
-
JDK-2129693 CMS should use Heap_lock for protecting heap resizing, instead of CMS token
- Resolved