JDK-8144949 : TestOptionsWithRanges -XX:NUMAInterleaveGranularity=2147483648 crashes VM
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2015-12-08
  • Updated: 2017-07-26
  • Resolved: 2015-12-21
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 9
9 b103Fixed
Related Reports
Relates :  
JDK-8145000 - TestOptionsWithRanges.java failure for XX:+UseNUMA -XX:+UseNUMAInterleaving -XX:NUMAInterleaveGranularity=65536
Relates :  
JDK-8142341 - GC: current flags need ranges to be implemented
Relates :  
JDK-8145027 - Exclude NUMAInterleaveGranularity from TestOptionsWithRanges.java
Description
 Internal Error (C:\\jprt\\T\\P1\\214445.cplummer\\s\\hotspot\\src\\share\\vm\\memory\\virtualspace.cpp:215), pid=119884, tid=55904
#  assert(partition_size <= size()) failed: partition failed
Comments
Bugs found by nightly testing. Verified by passed nightly.
26-07-2017
"java -server -XX:+UseNUMA -XX:+UseNUMAInterleaving -XX:NUMAInterleaveGranularity=2147483648 -version" triggers this assert. It is okay for '-client'. JDK-8142341 added a range for 'NUMAInterleaveGranularity' and this changed to test this flag by TestOptionsWithRanges.java. However, 'client' mode is only tested by default and nightly option rotation found this bug. The maximum available memory on Windows is 2G/8T (32bit/64bit). So 'range' should be changed. And we don't need current constraint function with this upper limit, as we will not get an overflow. With this upper limit, we still have a problem of not handling allocation failure. So we need to add checking allocation failure at CodeCache::reserve_heap_memory().
09-12-2015