If the cgroup_v1 container where you run the Java app is configured to have a memory limit higher than physically available on the host, the JVM might run with a higher-than-usual memory footprint.

This issue was fixed in the current release.
For the earlier releases, workarounds are to use `-XX:-UseContainerSupport` flag, use `-XX:MaxRAM=<physical_memory_amount>`, or apply a container limit that is smaller than the physical machine memory.