Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8207089 | 12 | Per Liden | P3 | Resolved | Fixed | b03 |
JDK-8207439 | 11.0.2 | Per Liden | P3 | Resolved | Fixed | b01 |
JDK-8207549 | 11.0.1 | Per Liden | P3 | Resolved | Fixed | b02 |
On Linux kernels < 3.17 (where memfd_create() syscall does not exist), ZGC falls back to searching for a suitable tmpfs mount point. If multiple mount points are found (which is the common case) we try to see if any of them matches the "preferred default" path (which is hard coded to be /dev/shm in ZGC). This work well, except on Debian and Debian derived distributions, which for some reason have chosen to use /run/shm instead instead of /dev/shm. As a result, ZGC will fail to initialize on some commonly used distributions (current Debian stable, Ubuntu 14.04-LTS, etc), forcing the user to manually mount a tmpfs file system on /dev/shm or use -XX:ZPath=/run/shm to explicitly select the mount point. ZGC should handle this situation much better, but having a list of preferred mount points (instead of just one) to allow for multiple alternatives covering differences between distributions. There is a high risk that this otherwise becomes a common problem, given the popularity of Debian and Debian derived distributions.
- backported by
-
JDK-8207089 ZGC: Preferred tmpfs mount point not found on Debian
-
- Resolved
-
-
JDK-8207439 ZGC: Preferred tmpfs mount point not found on Debian
-
- Resolved
-
-
JDK-8207549 ZGC: Preferred tmpfs mount point not found on Debian
-
- Resolved
-