Submit Feedback
Legacy Knowledge Base
Published 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

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

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
Did this article resolve your issue ?