Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FPM-PHP container memory leaks after daemon version v10.19.0.9 #938

Open
Anastasios89 opened this issue Jul 10, 2024 · 2 comments
Open

FPM-PHP container memory leaks after daemon version v10.19.0.9 #938

Anastasios89 opened this issue Jul 10, 2024 · 2 comments
Labels
bug Something isn't working support Redirect issue to support channels

Comments

@Anastasios89
Copy link

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

@Anastasios89 Anastasios89 added the bug Something isn't working label Jul 10, 2024
@workato-integration
Copy link

@bduranleau-nr bduranleau-nr added support Redirect issue to support channels and removed support Redirect issue to support channels labels Sep 16, 2024
@newrelic-php-agent-bot
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working support Redirect issue to support channels
Projects
None yet
Development

No branches or pull requests

3 participants