-
Bug
-
Resolution: Fixed
-
P3
-
6u4
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2177085 | 7 | Kevin Walls | P3 | Closed | Fixed | b27 |
JDK-2169560 | 6u10 | Kevin Walls | P3 | Resolved | Fixed | b27 |
JDK-2163839 | hs11 | Kevin Walls | P3 | Resolved | Fixed | b14 |
JDK-2164342 | hs10 | Kevin Walls | P3 | Resolved | Fixed | b24 |
with 6.0 u2. While we get a regular sawtooth curve in u2 we notice
with u4 that CMS for some reason seems to be unable to collect all
dead objects. The effect will be be over time more frequent CMS runs
which collect fewer and fewer objects. Used memory increases as well
as cpu consumption. However, later on, CMS is then suddenly able to
collect large chunks. Memory usage will go down. This scenario will
then repeat from the beginning.
Changed synopsis to reflect evaluation of root cause:
6u2+, 7b11+: CMS never clears referents when -XX:+ParallelRefProcEnabled
- backported by
-
JDK-2163839 6u4+, 7b11+: CMS never clears referents when -XX:+ParallelRefProcEnabled
-
- Resolved
-
-
JDK-2164342 6u4+, 7b11+: CMS never clears referents when -XX:+ParallelRefProcEnabled
-
- Resolved
-
-
JDK-2169560 6u4+, 7b11+: CMS never clears referents when -XX:+ParallelRefProcEnabled
-
- Resolved
-
-
JDK-2177085 6u4+, 7b11+: CMS never clears referents when -XX:+ParallelRefProcEnabled
-
- Closed
-
- duplicates
-
JDK-6698009 CMS is not collecting weak references when -XX:+ParallelRefProcEnabled
-
- Closed
-
- relates to
-
JDK-6752620 (audit) apply HSX-11 fix for 6662086 to HSX-12 and HSX-13
-
- Closed
-
-
JDK-6417901 Generalize parallel reference processing to all collectors.
-
- Resolved
-