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

Investigate rising use of memory which may indicate a leak #34809

Closed
roji opened this issue Oct 2, 2024 · 4 comments
Closed

Investigate rising use of memory which may indicate a leak #34809

roji opened this issue Oct 2, 2024 · 4 comments
Assignees
Labels
area-perf area-query closed-no-further-action The issue is closed and no further action is planned. customer-reported

Comments

@roji
Copy link
Member

roji commented Oct 2, 2024

See #34028 (comment)

@roji
Copy link
Member Author

roji commented Oct 3, 2024

@enanhgon can you please confirm whether you're actually getting an OutOfMemoryException via your repro?

@roji
Copy link
Member Author

roji commented Oct 8, 2024

/cc @renanhgon (typo above)

@renanhgon
Copy link

Hi @roji,

I was only able to reproduce the issue when running the application in containerized environments with specific memory limits.
When running it locally and pinging the mentioned route, I noticed a gradual increase in memory usage through diagnostic tools. However, even when applying the same memory limits locally as used in my pods, I couldn’t reproduce the OutOfMemoryException.

@roji
Copy link
Member Author

roji commented Oct 10, 2024

Whether you run the application in a containerized environment shouldn't have an impact here, aside from the memory limits that entails. I'll go ahead and close this for now as we don't have a repro or evidence of a problem - a gradual increase of memory usage is normal, as explained in #34028 - the GC will kick in as needed, according to its own considerations etc.

@roji roji closed this as not planned Won't fix, can't repro, duplicate, stale Oct 10, 2024
@roji roji added the closed-no-further-action The issue is closed and no further action is planned. label Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-perf area-query closed-no-further-action The issue is closed and no further action is planned. customer-reported
Projects
None yet
Development

No branches or pull requests

3 participants