Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8063435 | 8u45 | Jesper Wilhelmsson | P3 | Resolved | Fixed | b01 |
JDK-8057126 | 8u40 | Jesper Wilhelmsson | P3 | Resolved | Fixed | b05 |
JDK-8070986 | emb-8u47 | Jesper Wilhelmsson | P3 | Resolved | Fixed | team |
Scenario should like:
eat(area1); // allocated humongous objects in area1
committed1 = getCommitted();
eat(area2); // allocated humongous objects in area2
committed2 = getCommitted();
eat(area3); // allocated humongous objects in arae3
committed3 = getCommitted();
free(area1); // reclaim objects in area1
free(area2); // reclaim objects in area2
check( getCommitted() ~= committed1)
- backported by
-
JDK-8057126 CMM Testing: an allocated humongous object at the end of the heap should not prevents shrinking the heap
-
- Resolved
-
-
JDK-8063435 CMM Testing: an allocated humongous object at the end of the heap should not prevents shrinking the heap
-
- Resolved
-
-
JDK-8070986 CMM Testing: an allocated humongous object at the end of the heap should not prevents shrinking the heap
-
- Resolved
-
- relates to
-
JDK-8036025 Sort the freelist in order to shrink the heap
-
- Resolved
-
-
JDK-8041946 CMM Testing: 8u40 an allocated humongous object at the end of the heap should not prevents shrinking the heap
-
- Resolved
-