-
Bug
-
Resolution: Fixed
-
P1
-
hs14
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2175668 | 7 | Y. Ramakrishna | P3 | Closed | Fixed | b54 |
| JDK-2180578 | 6u18 | Y. Ramakrishna | P3 | Closed | Fixed | b01 |
| JDK-2175490 | 6u14 | Y. Ramakrishna | P1 | Resolved | Fixed | b05 |
| JDK-2175491 | hs15 | Y. Ramakrishna | P3 | Closed | Fixed | b05 |
The fix for 6819891 inadvertently introduced a memory leak, in
the C-heap, of the order of 2KB*ParallelGCThreads per scavenge.
Over a period of time such a leak can run the JVM out of C-heap
memory and lead to availability issues in the field.
This bug should be fixed in hs14 where it was first introduced.
The bug affects the 64-bit compressed oops jvm using the ParNew
(or CMS) collector.
the C-heap, of the order of 2KB*ParallelGCThreads per scavenge.
Over a period of time such a leak can run the JVM out of C-heap
memory and lead to availability issues in the field.
This bug should be fixed in hs14 where it was first introduced.
The bug affects the 64-bit compressed oops jvm using the ParNew
(or CMS) collector.
- backported by
-
JDK-2175490 ParNew: Fix memory leak introduced in 6819891
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-