You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have separated container for agent & daemon, after v10.19.0.9 including 10.22.0.12 we observed memory leaks on agent's container, in order to fix the issue we locked daemon to v10.18.0.8.
Note version of agent doesn't make any change.
Steps to Reproduce
Step 1: Upgrade daemon to v10.19.0.9+
Step 2: Restart agent's container, new agent's containers are started with memory leaks.
Your Environment
Docker image: php:8.3.6-fpm-bookworm
Deployed on EKS
The text was updated successfully, but these errors were encountered:
This issue has been identified as requiring additional information to debug. Due to the potentially sensitive nature of the information we may have to collect, such as PHPInfo and Debug Logs, please follow these steps to create a support case, where a member of our New Relic Support Team will work with you to gather the necessary information securely and help debug your issue.
If your subscription level does not include technical support, the other option available to customers is to use New Relic’s community support channel: Explorers Hub. From there, a member of our New Relic Support Team will work with you to gather the necessary information securely and help debug your issue. For all available options on how to get support, please see these resources.
Description
We have separated container for agent & daemon, after v10.19.0.9 including 10.22.0.12 we observed memory leaks on agent's container, in order to fix the issue we locked daemon to v10.18.0.8.
Note version of agent doesn't make any change.
Steps to Reproduce
Step 1: Upgrade daemon to v10.19.0.9+
Step 2: Restart agent's container, new agent's containers are started with memory leaks.
Your Environment
Docker image: php:8.3.6-fpm-bookworm
Deployed on EKS
The text was updated successfully, but these errors were encountered: