JDK-8176573 : Do not use FLAG_SET_ERGO to update MaxRAM for emulated client
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 9,10
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2017-03-13
  • Updated: 2019-09-13
  • Resolved: 2017-03-14
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 10 JDK 9
10Fixed 9 b163Fixed
Related Reports
Relates :  
JDK-8166002 - Emulate client build on platforms with reduced virtual address space
Description
setting MaxRAM FLAG_SET_ERGO affects Arguments::set_heap_size inappropriately,

void Arguments::set_heap_size() {
  julong phys_mem =
    FLAG_IS_DEFAULT(MaxRAM) ? MIN2(os::physical_memory(), (julong)MaxRAM)
                            : (julong)MaxRAM;

so, do not use FLAG_SET_ERGO to update MaxRAM for emulated client
Comments
ILW = Emulated client changes MaxRAM inappropriately that may unexpectedly affect the heap size, all VM instances running in emulated client mode, no workaround = MHH = P2
13-03-2017