JDK-8037925 : CMM Testing: an allocated humongous object at the end of the heap should not prevents shrinking the heap
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 7,8,9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2014-03-20
  • Updated: 2015-01-21
  • Resolved: 2014-04-15
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.

To download the current JDK release, click here.
JDK 8 JDK 9
8u40Fixed 9 b12Fixed
Related Reports
Relates :  
JDK-8041946 - CMM Testing: 8u40 an allocated humongous object at the end of the heap should not prevents shrinking the heap
Relates :  
JDK-8036025 - Sort the freelist in order to shrink the heap
Description
Need a test checking that allocating new humongous objects doesn't prevent g1 from shrinking area allocated earlier and recently reclaimed.

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)