Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Java processes don't use flags for correct heap sizing within docker

See original GitHub issue

See https://blog.csanchez.org/2017/05/31/running-a-jvm-in-a-container-without-getting-killed/.

The -XX:+UseCGroupMemoryLimitForHeap flag seems to be enabled by default on newer versions of openjdk:8:

docker run --rm -m 100MB openjdk:8u212 java -XshowSettings:vm -version

but the public base-java still uses an older one that would need the manual flag:

docker run --rm -m 100MB jitsi/base-java java -XshowSettings:vm -version

This can cause unexpected out of memory / crashes.

The container support has been further improved in JDK 10:

Issue Analytics

State:
Created 4 years ago
Comments:12 (6 by maintainers)

Top GitHub Comments

1reaction

bkempecommented, Jun 29, 2019

BTW, this is a helpful tool for setting the JVM memory sizes correctly within docker: https://github.com/cloudfoundry/java-buildpack-memory-calculator https://github.com/meisterplan/jdk-base is a docker image that also uses these calculations

1reaction

damenchocommented, May 7, 2019

Jigasi is setting JIGASI_MAX_MEMORY=3072m. And by the way, I’ve tested java11 and I’m currently pushing PRs so we can run using java11. Trying to push it these days, release on meet.jit.si and push it to stable.