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

untracked memory or a leak #3342

Open
romange opened this issue Jul 19, 2024 · 2 comments
Open

untracked memory or a leak #3342

romange opened this issue Jul 19, 2024 · 2 comments
Assignees
Labels
bug Something isn't working important higher priority than the usual ongoing development tasks

Comments

@romange
Copy link
Collaborator

romange commented Jul 19, 2024

A dragonfly process slowly grows in RSS while used memory stays stable.
See the attached files:

info log + arena logs:
info_all_101208.txt
arena_101208.txt
arena_backing_101208.txt

The process uses 16 threads. These show that the leakage is in the backing arena. Further analysis shows that most of the arena memory is spent on allocations with sizes higher than 3000.

Allocation tracking of memory track add 3000 20000 1
jdbfly.txt.tar.gz

More investigations is needed.

@romange romange added bug Something isn't working important higher priority than the usual ongoing development tasks labels Jul 19, 2024
@romange
Copy link
Collaborator Author

romange commented Jul 19, 2024

My working assumption is that we do not track/clean up redis parser memory. I see lots of memory allocations coming from there.
maybe even we have a bug that causes the parser to allocate more and more.

@romange
Copy link
Collaborator Author

romange commented Jul 20, 2024

It seems that we track redis parser correctly. I am attaching more allocation logs but now it seems more and more like a leak.

alloc_log.txt.gz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working important higher priority than the usual ongoing development tasks
Projects
None yet
Development

No branches or pull requests

1 participant