If you build JDK on a machime with 4k pages, and then move it to machine with 64k pages, java will not start (see below).
The problem goes away if you rebuild CDS archive.
*This bug has signisficant impact to development process.*
Running a simple java -version results:
./jdk/bin/java -version
[0.015s][error][cds] Unable to map CDS archive -- os::vm_allocation_granularity() expected: 4096 actual: 65536
openjdk version "14-internal"
OpenJDK Runtime Environment (build 14-internal+0-adhoc.jenkins.jdk-dev-nightly)
The problem goes away if you rebuild CDS archive.
*This bug has signisficant impact to development process.*
Running a simple java -version results:
./jdk/bin/java -version
[0.015s][error][cds] Unable to map CDS archive -- os::vm_allocation_granularity() expected: 4096 actual: 65536
openjdk version "14-internal"
OpenJDK Runtime Environment (build 14-internal+0-adhoc.jenkins.jdk-dev-nightly)
- is blocked by
-
JDK-8243392 Remodel CDS/Metaspace storage reservation
-
- Resolved
-
- relates to
-
JDK-8230645 CDS regions get loaded with the wrong alignment
-
- Resolved
-
-
JDK-8231610 Relocate the CDS archive if it cannot be mapped to the requested address
-
- Resolved
-