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

Possible memory leak on version v0.41.x #2884

Open
garutilorenzo opened this issue Oct 29, 2024 · 2 comments
Open

Possible memory leak on version v0.41.x #2884

garutilorenzo opened this issue Oct 29, 2024 · 2 comments
Labels

Comments

@garutilorenzo
Copy link

Describe the bug
It seems to be a memory leak somewhere with version v0.41.x.
With earlier releases we never experienced any memory problem. We are using aws-otel-collector to send opentelemetry traces to a remote endpoint (Coralogix).
From 10 days our fargate container is crashing due to memory usage.
We haven't released any new application version, and the application traffic is unchanged.
We are using "latest" tag on our task definition, and we are not using a specific version tag.

Our dev environment that is using version v0.40.2 is not affected by the problem.

Here the container is reaching the max memory usage (1GB).
Fargate kills the container and restart the service

image

What did you expect to see?
Constant memory usage.

What did you see instead?
Random spike in memory usage

Environment
We are using aws-otel-collector as a fargate service to send opentelemetry traces to a remote endpoint (Coralogix).
We are using "latest" tag on our task definition, and we are not usign a specifig version tag.

Additional context
N/A

@garutilorenzo
Copy link
Author

Adding more information.
We tried to upgrade our dev environment from v0.40.2 to v0.41.1 (latest).

This is the result:

image

There is clear memory increase and is growing constantly

Copy link
Contributor

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale label Dec 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant