legacy-knowledge-base
公開されました Jun. 30, 2025

Native OS memory, allocated to JVM threads, does not get released completely

written-by

Balázs Létai

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

legacy-article

learn-legacy-article-disclaimer-text

Issue

  • The memory used by the Liferay Docker container slowly, but steadily increases, until either the pod goes out-of-memory, or the pod alerts trigger a kill of the pod.

Environment

  • Liferay Quarterly releases

Resolution

  • Change the malloc implementation by using the DOCKER_TCMALLOC_ENABLED environment variable.
  • In our SaaS offerings we have this by default.
  • Github link
did-this-article-resolve-your-issue

legacy-knowledge-base