Restartable sequences (rseq), which are used by glibc, are known to cause problems on restore and checkpoint in some environments.
A workaround is to disable rseq in glibc when CRaC is used. This can be done by the launcher automatically for better user experience.
Alternatives like more clever detection of rseq, or detection of a problematic environment seem too complex, having that positive impact from rseq on Java performance is expected to be negligible.
A workaround is to disable rseq in glibc when CRaC is used. This can be done by the launcher automatically for better user experience.
Alternatives like more clever detection of rseq, or detection of a problematic environment seem too complex, having that positive impact from rseq on Java performance is expected to be negligible.
- relates to
-
JDK-8349131 [CRaC] Internal error on old glibc with pre-set GLIBC_TUNABLES and CPUFeatures restriction
-
- Resolved
-
- links to
-
Commit(crac)
openjdk/crac/df8b731b
-
Review(crac)
openjdk/crac/199