Skip to content

Memory leak in AWS Fargate #4327

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

Open
InterstellarStella opened this issue Apr 25, 2025 · 2 comments
Open

Memory leak in AWS Fargate #4327

InterstellarStella opened this issue Apr 25, 2025 · 2 comments
Labels

Comments

@InterstellarStella
Copy link

InterstellarStella commented Apr 25, 2025

How do you use Sentry?

Sentry Saas (sentry.io)

Version

2.14.0

Steps to Reproduce

This issue is created on behalf of the customer.

We are using Sentry Python SDK in our FastAPI application, and we have discovered that it might be causing some memory leaks in our web server where a lot of memory is retained in primary memory and not being released. We also saw an open issue on GitHub where Logger.exception causes memory leaks.

So we are kind of hoping to understand if we can resolve this and stick to Sentry because this is causing issues on our server.

Further information is provided in the shadow ticket.

Expected Result

No memory leaks.

Actual Result

Using the Sentry SDK causes memory leaks. Graphs are provided in the shadow ticket.

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Apr 25, 2025
@InterstellarStella
Copy link
Author

@szokeasaurusrex
Copy link
Member

Hello! Thank you for reaching out.

Could you please try the following and let us know whether it fixes the problem?

  1. First, please try upgrading to the latest version of the Sentry SDK, in case we might have already fixed the underlying issue.
  2. Second, if upgrading does not fix the problem, please try disabling the DedupeIntegration. This was suggested as a workaround in the logging.exception memory leak issue (Memory leak during exception logging #3165). If disabling DedupeIntegration fixes the memory leak, then we can close this issue as a duplicate of Memory leak during exception logging #3165

If neither of those suggestions help, please let me know, and we can continue debugging from there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

3 participants